[notify-pr-bot]

Summary

Copy Rendered Summary

NOTIFICATION-API

• #3053 - Revert "Summoning heavenly logging to smite mismatches on priority assignment…" — Jimmy Royer

Component	Changes
NOTIFICATION-ADMIN	No new commits
NOTIFICATION-API	- Revert "Summoning heavenly logging to smite mismatches on priority assignment…" (#3053) by Jimmy Royer
NOTIFICATION-DOCUMENT-DOWNLOAD-API	No new commits
NOTIFICATION-DOCUMENTATION	No new commits
NOTIFICATION-LAMBDAS	No new commits
NOTIFICATION-MANIFESTS	No new commits

Type of change

• Releasing a new version of Notify
• Kubernetes / Helm configuration change
• Dependency or container image update
• Breaking change (requires downtime or a maintenance window)
• Other: ___

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] or [AUTO-PR] - 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.

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

• API
• Admin
• Documentation
• Document download API
• notification-lambdas

Pre-merge checklist

• Changes have been verified in Notify staging
• I have checked if the docker images I am referencing exist
  • api k8s
  • admin
  • documentation
  • document download API
  • notification-lambdas (heartbeat, ses_to_sqs_email_callbacks, system-status)
• If this PR changes Kubernetes config, I know how to get kubectl credentials in case it catches on fire

Post-merge checklist

• 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.