Make a Release: 2023.03.2

[angela-tran]

Release manager

@angela-tran

Release version

2023.03.2

What type of release is this?

Regular

Release checklist

• Create a branch called release/version from the source branch
• Bump the application version
• Open a PR for the release branch into the staging target, merge - Prepare Release 2023.03.2 #1331
• (If applicable): update staging data migrations dev secrets are up-to-date
• (If applicable): open another PR from dev to test - Deploy 2023.03.2 to test #1332
• (If applicable): update data migrations - I updated the auth scope for the test Key Vault and checked over most of the secrets that will be used by the data migration - looks good ✅ - edit: we needed to make fix Chore: make active flag configurable for SacRT agency #1337
• QA the app in test
• (If applicable): prepare production data migrations verified secrets in prod key vault
• Open a PR to for the test branch into prod, merge - Release 2023.03.2 #1341
• QA the app in prod - noticed there was a read timeout on a call to eligibility-server, worked when we tried it again. Will fix in a follow-up PR
• Tag the release on the prod branch, push the tag to GitHub
• Create a release in GitHub for the tag, generating release notes
• Edit release notes with additional context, images, animations, etc. as-needed

[angela-tran]

I am planning on working on this on Monday (March 27)

[angela-tran]

Reminder @angela-tran : update the auth scope secret for test and prod before deploying to them! See cal-itp/benefits-secrets#20 for more context

[angela-tran]

Finished this yesterday with release 2023.03.2, and now closing