[AUTO-PR] Automatically generated new release 2024-07-30T13:20:24.635Z

[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] 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.

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

• Fix process type for alert category (#2232) by Jumana B
• Reorg flask commands (#2234) by Steve Astels

NOTIFICATION-ADMIN

• Clear cache when a Template Category is updated (#1912) by William B
• Run unit tests using multiple configurations (#1903) by Andrew
• add fr translation for review (#1913) by Jumana B
• Fix/template-platform-admin-check (#1909) by Andrew
• Do not display hidden template categories (#1911) by Andrew

NOTIFICATION-DOCUMENT-DOWNLOAD-API

NOTIFICATION-DOCUMENTATION

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.

[github-actions]

ingress	nginx    	2       	2024-02-12 19:08:42.93215444 +0000 UTC	deployed	nginx-ingress-1.1.2	3.4.2      

xray-daemon	xray     	1       	2024-07-29 19:45:48.684608347 +0000 UTC	deployed	aws-xray-4.0.8	3.3.12     

Comparing release=karpenter-crd, chart=/tmp/helmfile3223172515/karpenter/staging/karpenter-crd/karpenter-crd/0.36.1/karpenter-crd
Comparing release=karpenter, chart=/tmp/helmfile3223172515/karpenter/staging/karpenter/karpenter/0.36.1/karpenter
Comparing release=karpenter-nodepool, chart=charts/karpenter-nodepool
Comparing release=priority-classes, chart=deliveryhero/priority-class
Comparing release=secrets-store-csi-driver, chart=secrets-store-csi-driver/secrets-store-csi-driver
Comparing release=aws-secrets-provider, chart=aws-secrets-manager/secrets-store-csi-driver-provider-aws
Comparing release=kube-state-metrics, chart=prometheus-community/kube-state-metrics
Comparing release=blazer, chart=stakater/application
Comparing release=ingress, chart=charts/nginx-ingress
Comparing release=xray-daemon, chart=okgolove/aws-xray