Release Management

Purpose

Ensure releases are predictable, observable, and reversible.

Inputs

• Approved change(s)
• Verified test results

Procedure

1. Ensure service tests pass (uv run pytest or service-specific tests).
2. Merge to main to trigger automated builds and dev deployments (no additional approvals).
3. Use Cloud Deploy to promote to production (approval required for prod).
4. Monitor Cloud Run logs and error rates after rollout.
5. Roll back via Cloud Deploy if regressions appear.

Notes

• There is no standard release note or changelog requirement.
• Use feature flags (Statsig) for risky changes and default them to off.