Production Release Signoff¶
Last audited: 2026-05-30.
Use this before manually advancing production from integration.
Branch Gate¶
Release worktree checklist reviewed:
release-worktree-checklist.md.
git fetch --all --prune
git rev-list --count origin/integration..origin/production
git merge-base --is-ancestor origin/production origin/integration
The count must be 0; production must be an ancestor of integration.
Required Release Identity¶
- Release SHA: exact
origin/integrationcommit promoted to production. - Backend image tag: commit tag, not
latest. - Backend runtime:
APP_VERSION=<release-sha>,ENVIRONMENT=production,NEW_RELIC_APP_NAME=mamnajem-production-backend, and the privateNEW_RELIC_LICENSE_KEYthrough the approved runtime credential path. - Web-admin runtime:
VITE_APP_ENV=production,VITE_SOURCE_SHA=<release-sha>, the checksummedMAMNAJEM_STAGING_CLIENT_CONTRACT_FILEandMAMNAJEM_ADMIN_RUNTIME_CONTRACT_FILE; browser application binding comes from the sealed contract. - Mobile runtime, when deployed: production app/API URLs, exact native build number and the environment/platform-specific New Relic application token from the sealed client contract. Use the existing New Relic release helper and diagnostics verifier; do not introduce ad hoc provider variables.
Pre-Deploy Checks¶
- Integration pipeline is green at the release SHA.
- Release worktree checklist reviewed for each release-affecting repository.
- Backend unit/integration tests, security scans, and API compatibility checks passed.
- Mobile
pnpm check, Jest, and release config assertions passed if changed. - Web-admin
pnpm testandpnpm buildpassed if changed. - Architecture validation passed if Terraform changed.
- No active
SEV1or unresolved payment/subscription incident.
Deploy Watch¶
For 30 minutes after deploy, watch:
- Health alarm and
/actuator/health - API 5xx and unhealthy target alarms
- New Relic new/regressed backend and web-admin issues for the release SHA
- New Relic new/regressed mobile issues for the mobile release/dist when mobile changed
- Stripe webhook
DEAD,RETRYABLE, and oldest retry age - User reports and admin problem reports
No-Go Conditions¶
- Production-only commits exist.
- Release identity cannot be tied to a commit SHA.
- Required New Relic/runtime env vars are missing.
- Integration has unresolved payment, subscription, auth, or data integrity failures.
- A rollback path is not known before starting deploy.