Entities Release 29.5a

[meawong]

Prior to moving into production, the following steps should be completed or confirmed:

• Add release # to this ticket
• Create a Release Report Link Here
• Update version numbers in the code being released and list them here:
  • Business API v2.171.10
  • Business Filer v3.0.19
• Create a draft releases in GitHub:
  1. Confirm the correct commits are present
  2. Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a
     reference to a branch
  3. Autogenerate release notes using last release tag as a point of reference. Update change list manually if required.
• Ensure that the commit list is represented on the Release Report
  1. tag all respective tickets to current release
• Ensure deployment steps are filled in - remove/replace placeholders
• Post message that projects are being deployed to Test in "Entities Product Team" channel
• Deploy the code to Test (STEPS BELOW)
• Deploy the code to SANDBOX (STEPS BELOW)
  • wait time before moving on to prod should be:
    • 7 days for patch release
    • 30 days for minor or major release
• Dev/QA chat to plan Prod verification testing (unless already automated)
• Post message that projects are being deployed to Prod in "Entities Product Team" channel
• Deploy the code to Production (STEPS BELOW)
• Post message that projects have been deployed to Prod in "Entities Product Team" and "Modern OPS Team" channels
• Complete smoke test (STEPS BELOW)
• Finalize/publish the releases in GitHub (including tagging them)
• Close the Zenhub release report when complete
• Move this ticket to Done when complete

Deployment Steps

Dev:

• Business API v2.171.10 - Done by CD
• Business Filer v3.0.19 - Done by CD
  .
• any 1Pass env key changes? No
• are there any dependencies, such as an auth/pay deployment or keycloak changes? No
• are there any one-time scripts to be run, such as for data migration? No
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook? No
• feature flag additions/removals and values set appropriately? No

Test:

• Business API v2.171.10 - Done by MW on June 11
• Business Filer v3.0.19 - Done by MW on June 11
  .
• any 1Pass env key changes? No
• are there any dependencies, such as an auth/pay deployment or keycloak changes? No
• are there any one-time scripts to be run, such as for data migration? No
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook? No
• feature flag additions/removals and values set appropriately? No

Prod:

• Business API v2.171.10 - Done by
• Business Filer v3.0.19 - Done by

.

• any 1Pass env key changes? No
• are there any dependencies, such as an auth/pay deployment or keycloak changes? No
• are there any one-time scripts to be run, such as for data migration? No
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook? No
• feature flag additions/removals and values set appropriately? No

Smoke Test Script

• load BRD UI, eg, see list of businesses
• load Business Dashboard UI, eg, view business
• load Business Filings UI, eg, start COA or COD
• load Business Edit UI, eg, start change or alteration filing
• load Business Create UI, eg, start an IA or registration or voluntary dissolution
• watch logs in GCP for 60 minutes (https://console.cloud.google.com/logs/)