Rollback

Owner: DevOps
Reviewers: Engineering, QA
Status: Draft
Version: 0.1
Last Updated: 2026-09-16
Review Cycle: Per deployment change

Rollback Principles

• Roll back application image first when schema remains compatible.
• Treat irreversible database migrations as release blockers unless a compensating plan exists.
• Keep release notes and migration notes together.

Backend Rollback Checklist

1. Identify previous healthy image tag.
2. Confirm database compatibility.
3. Update Kubernetes manifest/image tag.
4. Apply the overlay.
5. Verify /api/health and critical API smoke tests.
6. Record incident and follow-up actions.

Open Items

• Confirm artifact registry retention.
• Define database rollback/restore policy.
• Define owner approval for production rollback.