Entities Sprint 19.7a Release

[severinbeauvais]

• Scheduled for Test on January 9, 2024
• Scheduled for Prod on January 11, 2024

link to release report

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

• Tag the release to this ticket
• Update version numbers in the code being released and list them here:
  • Business Create UI v5.6.29
  • Business Filings UI v7.0.32
  • Business Edit UI v4.7.15
  • Legal API v2.99.0
• Ensure deployment steps are filled in - remove/replace placeholders
• Create draft releases in GitHub and confirm the correct commits are present

1. Confirm the correct commits are present
2. Select appropriate target 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.

• Dev to ensure that the commit list is represented on the release report
• QA to schedule the release with staff/clients (daytime's best or when staff are available for rollback)
• All dev/test pipeline test suites green
• 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
• Release the code to production and complete smoke test (STEPS BELOW)
• Post message that projects have been deployed to Prod in Entities Product Team channel and OPS Team channel
• Finalise/publish the releases in GitHub, tagging it
• Merge release branch back to master (if applicable)
• Change openshift builds/pipelines back to master (if applicable)

Deployment Steps

Dev:

• Create UI v5.6.29 - done by CD script
• Filings UI v7.0.32 - done by CD script
• Edit UI v4.7.15 - done by CD script
• Legal API v2.99.0 - done by CD script
  .
• verify that both Legal API: return "displayLedger" flag in filings results #18490 and Filings UI: Admin Freeze should not show on ledger #16967 are included (dependency)
• config map changes
• are there any dependencies, such as an auth/pay deployment or keycloak changes?
• are there any one-time scripts to be run, such as for data migration?
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook
  • Added amalgamation table
  • Added amalgamating_business table
  • Verify version_num field in alembic_version table has value of f978e34aa8bb

Test:

• Create UI v5.6.29 - done by JG on January 9
• Filings UI v7.0.32 - done by JG on January 9
• Edit UI v4.7.15 - done by JG on January 9
• Legal API v2.99.0 - done by JG on January 9
  .
• verify that both Legal API: return "displayLedger" flag in filings results #18490 and Filings UI: Admin Freeze should not show on ledger #16967 are included (dependency)
• config map changes
• are there any dependencies, such as an auth/pay deployment or keycloak changes?
• are there any one-time scripts to be run, such as for data migration?
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook
  • Added amalgamation table
  • Added amalgamating_business table
  • Verify version_num field in alembic_version table has value of f978e34aa8bb

Prod:

• Create UI v5.6.29 - done by JG on January 11
• Filings UI v7.0.32 - done by JG on January 11
• Edit UI v4.7.15 - done by JG on January 11
• Legal API v2.99.0 - done by JG on January 11
  .
• config map changes
• are there any dependencies, such as an auth/pay deployment or keycloak changes?
• are there any one-time scripts to be run, such as for data migration?
• database updates which should be run automatically as part of GH CD via the legal-api pre-hook
  • Added amalgamation table
  • Added amalgamating_business table
  • Verify version_num field in alembic_version table has value of f978e34aa8bb
• enable Digital Credentials FF in Prod - done by SB
  .
• notify the team via the OPS Team channel

Smoke Test Script

• load Filings UI
• load Edit UI, eg, start change or alteration filing
• load Create UI, eg, start an IA or registration or voluntary dissolution
• watch Sentry logs for 60 minutes
• watch Kibana logs for 60 minutes