Release Tracker v4.15.0

[elipe17]

Release v4.15.0

CONTENT:

🔗 Included Pull Requests (Dev Team)

• Remove RPT_MONTH_YEAR Validators from S3 & S4 Records by @elipe17 in Remove RPT_MONTH_YEAR Validators from S3 & S4 Records #5645
• Unique Log File Per Parse by @elipe17 in Unique Log File Per Parse #5658
• 5642 - Add reprocessed modal to FRA Submission History by @jtimpe in 5642 - Add reprocessed modal to FRA Submission History #5659
• 5421 e2e tests for admin feedback reports by @mattcoleanderson in 5421 e2e tests for admin feedback reports #5637
• 5508 migrate from npm to yarn by @raftmsohani in 5508 migrate from npm to yarn #5633
• Model Auditing/Versioning by @elipe17 in Model Auditing/Versioning #5647
• 5541 - feature flag hooks by @jtimpe in 5541 - feature flag hooks #5650
• 5661 - PIA feature flag by @jtimpe in 5661 - PIA feature flag #5671
• Digit Sensitive Role by @elipe17 in Digit Sensitive Role #5667
• Missing Parser Error Indexes by @elipe17 in Missing Parser Error Indexes #5684
• Go Parser High Level Architecture by @elipe17 in Go Parser High Level Architecture #5639
• Fix: delete local parser log files after S3 upload by @elipe17 in Fix: delete local parser log files after S3 upload #5682
• add level to the stage.labels block by @mattcoleanderson in add level to the stage.labels block #5678
• [BUGFIX] revert REDIS_URI back to using django's CELERY_BROKER_URL setting by @mattcoleanderson in [BUGFIX] revert REDIS_URI back to using django's CELERY_BROKER_URL setting #5674
• 5490 display requested changes in profile page by @raftmsohani in 5490 display requested changes in profile page #5626
• Add issue template for Release Tracker by @kennymcnett in Add issue template for Release Tracker #5656
• Rename PermissionGuard to AccessGuard by @jtimpe in Rename PermissionGuard to AccessGuard #5677
• Fix cypress deploy failures by @jtimpe in Fix cypress deploy failures #5680
• implement regional feedback reports support by @mattcoleanderson in implement regional feedback reports support #5666

➡️ URL of GitHub Release Tag:

https://github.com/raft-tech/TANF-app/releases/tag/v4.15.0

---

📦 1. Preparation & Handoff (Dev / UX / PM)

Ensuring the release branch is ready and documented before ACF takes over.

• Release Tagged: develop branch tagged with the new release version.
• Release Branch Created: Branch cut from develop.
• PR Opened to Staging: PR opened from the release branch to HHS:main.
• Testing Instructions Verified: All linked PRs contain clear testing instructions for ACF validation.
• UX/Documentation Check: UX team has reviewed the PRs, confirmed user-facing changes, and started drafting Release Notes and Knowledge Center guidance.
• Migration Flag: Does this release include a database migration? [Yes / No] (If Yes, rollback from production will be highly complex).
• Handoff Complete: Issue assigned to @ADPennington for Staging validation.

---

🧪 2. Staging Validation & QASP (ACF / Alex)

Tracking the status once ACF takes over deployment and testing.

Before you Deploy

• Requires base image updates:
  • Re-tag ghcr.io/raft-tech/tdp-frontend-base:v1.1.0 for the HHS GHCR instance
• Requires HHS CircleCI config updates:
  • Add environment variable for the digit sensitive Postgres user password
• Requires PLG deployment

Staging Deployment

• Staging Cleared: Team notified that Staging is about to be updated/restarted.
• Deployed to Staging: PR merged and deployed to the Staging environment.
• Feature Validation: Testing instructions from the linked PRs have been executed and passed.
• Regression Validation: Core workflows (login, submissions, data integrity, etc.) remain functional.

🐛 Bug Tracking Protocol (If issues are found in Staging):

1. Non-Dev Team: Add a comment on this issue describing the bug/unexpected behavior.
2. Dev Team: Review the comment, investigate root cause, and open a formal GitHub Issue.
3. Triage Decision:
   • Revert: If isolated to a new feature, revert the PR out of the release candidate.
   • Hotfix: Warranted only if the bug blocks the release entirely AND the production release is needed ASAP. (Dev cuts hotfix PR against the release branch -> merged to HHS:main for re-testing).

• Documentation Finalized: UX team confirms all Release Notes and Knowledge Center updates are finalized and ready for launch.

---

🚦 3. Production-Ready Sign-Off

• ACF/Alex confirms all PRs are validated, no blocking bugs exist, documentation is finalized, and the release is approved for production deployment.

---

🛟 4. Rollback & Contingency Reference

Review before production deployment.

• Pipeline/CircleCI Failure: Retry the pipeline. If it fails again, requires a hotfix to unblock.
• Missing Config/Secrets (App crashes on boot): Do not rollback. ACF updates environment variables in the production console and restarts the app.
• Third-Party API Blocked in Prod: Dev provides an emergency hotfix to hide the broken UI component.
• Performance/Database Lockup Under Load: Dev writes an emergency hotfix for the offending query.
• Critical Regression Post-Deploy:
  • No migrations in release: Rollback the deployment to the previous stable version.
  • Migrations in release: Rollback is generally not possible; requires an emergency hotfix.

---

🚀 5. Production Deployment (ACF / Alex)

The final deployment executed by ACF.

• Maintenance Mode: Alex has enabled the maintenance page to ensure users are out of the system.
• Deployed to Prod: PR opened and merged to HHS:master, triggering deployment.
• Post-Launch Verification: Quick check that the production environment is stable post-deploy, and the maintenance page is deactivated.

---

📢 6. Post-Release Communication (PM / UX / ACF)

Closing the loop with users and stakeholders.

• Release Notes Published: (UX team) Plain-language, user-facing release notes and Knowledge Center guidance have been published.
• Stakeholders Notified: (ACF) Any required external communication regarding the new version has been sent.
• Close this Issue: (ACF / PM) The release is fully deployed and stable.