feat(canary): rollback script + release-pipeline doc (Phase 4) - #989
Merged
Merged
Conversation
Closes the canary loop with the escape hatch and a single place to
read about the whole flow.
scripts/rollback-latest.sh <sha>
uses crane to retag :latest ← :staging-<sha> for BOTH the platform
and tenant images. Pre-checks the target tag exists and verifies
the :latest digest after the move so a bad ops typo doesn't
silently promote the wrong thing. Prod tenants auto-update to the
rolled-back digest within their 5-min cycle. Exit codes: 0 = both
retagged, 1 = registry/tag error, 2 = usage error.
docs/architecture/canary-release.md
The one-page map of the pipeline: how PR → main → staging-<sha> →
canary smoke → :latest promotion works end-to-end, how to add a
canary tenant, how to roll back, and what this gate explicitly does
NOT catch (prod-only data, config drift, cross-tenant bugs).
No code changes in the CP or workspace-server — this PR is shell
+ docs only, so it's safe to land independently of the other Phase
{1,1.5,2,3} PRs still in review.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
molecule-ai Bot
pushed a commit
that referenced
this pull request
Apr 21, 2026
feat(canary): rollback script + release-pipeline doc (Phase 4)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Last piece of the canary workstream. Adds the manual escape hatch + a single doc to point new ops at.
What's in
`scripts/rollback-latest.sh ` — uses `crane` to retag `:latest` ← `:staging-` for both the platform + tenant images. Pre-checks the target tag exists and verifies the `:latest` digest after the move so a typo can't silently promote the wrong thing. Prod tenants auto-update within 5 min.
`docs/architecture/canary-release.md` — the one-page map of the pipeline: how PR → main → `:staging-` → canary smoke → `:latest` works, how to add a canary tenant, how to roll back, and what the gate explicitly does NOT catch (prod-only data, config drift, cross-tenant bugs).
Why shell-only
No code in CP or workspace-server. Safe to land independently of Phase 1.5/2/3 PRs still in review.
Test plan
🤖 Generated with Claude Code