Merge to production: one continuous, queryable record.
Every Release and Rollout is a durable Cloud Deploy resource — no separate tracking system needed.
1
Release createdCloud Build finishes, pushes the image
2
Dev rolloutRuns automatically, no gate
3
Auto-promote to stagingAutomation rule, zero human trigger
4
Prod rollout pausedrequireApproval — waits for a human
5
Canary + rollback watch25% → verify → 50% → verify → 100%
Best practice: don't build a parallel tracking spreadsheet — Cloud Deploy's own history plus Cloud Audit Logs already answers "what's running, since when, promoted by whom."