[AUTO-PR] Automatically generated new release 2023-09-28T19:37:58.188Z

[notify-pr-bot]

What happens when your PR merges?

• Prefix the title of your PR:
  • fix: - tag main as a new patch release
  • feat: - tag main as a new minor release
  • BREAKING CHANGE: - tag main as a new major release
  • [MANIFEST] - tag main as a new patch release and deploy to production
  • chore: - use for changes to non-app code (ex: GitHub actions)
• Alternatively, change the VERSION file - this will not create a new tag, but rather will release the tag in VERSION to production.

What are you changing?

• Releasing a new version of Notify
• Changing kubernetes configuration

Provide some background on the changes

⚠️ The production version of the Terraform infrastructure is behind the latest staging version. Consider upgrading to the latest version before merging this pull request.

⚠️ The production version of manifests is behind the latest staging version. Consider upgrading to the latest version before merging this pull request.

NOTIFICATION-API

• chore: synced file(s) with cds-snc/site-reliability-engineering (#1968) by sre-read-write[bot]

NOTIFICATION-ADMIN

• chore: synced file(s) with cds-snc/site-reliability-engineering (#1655) by sre-read-write[bot]

NOTIFICATION-DOCUMENT-DOWNLOAD-API

• chore: synced file(s) with cds-snc/site-reliability-engineering (#145) by sre-read-write[bot]

NOTIFICATION-DOCUMENTATION

• chore: synced file(s) with cds-snc/site-reliability-engineering (#134) by sre-read-write[bot]

If you are releasing a new version of Notify, what components are you updating

• API
• Admin
• Documentation
• Document download API

Checklist if releasing new version:

• I made sure that the changes are as expected in Notify staging
• I have checked if the docker images I am referencing exist
  • api lambda (requires Notification-Production / AdministratorAccess login)
  • api k8s
  • admin
  • documentation
  • document download API

Checklist if making changes to Kubernetes:

• I know how to get kubectl credentials in case it catches on fire

After merging this PR

• I have verified that the tests / deployment actions succeeded
• I have verified that any affected pods were restarted successfully
• I have verified that I can still log into Notify production
• I have verified that the smoke tests still pass on production
• I have communicated the release in the #notify Slack channel.