ci(sandbox): auto-bump deco-apps-cd on studio-sandbox image release#4272
Merged
Conversation
The sandbox image is built + pushed on every merge to main touching packages/sandbox/**, but nothing bumped the tag in deco-apps-cd, so the new version never rolled out without a manual edit. Add a bump-deco-apps-cd job that fires the generic `image-bump` repository_dispatch (deco-apps-cd's bump-image.yml receiver) with the new version + the studio-sandbox image anchor + the stg/prod sandbox values files. Mirrors release-mesh.yaml's dispatch pattern (same DEPLOY_REPO_TOKEN, no cross-repo write credential here). Only fires when a new image was actually pushed; no-ops if the token is absent.
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
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.
Problem
Merging any change to
packages/sandbox/**on main builds + pushes a newstudio-sandboximage (release-studio-sandbox.yaml), but nothing bumps the tag in deco-apps-cd, so the release never rolls out without a manual values edit. (Chart default is1.6.1; deco-apps-cd is hand-bumped to1.9.0— the drift is the symptom.)Fix
Add a
bump-deco-apps-cdjob that fires the genericimage-bumprepository_dispatch already implemented in deco-apps-cd (bump-image.yml), which surgically rewrites thetag:under the matchingrepository:line and self-commits. Payload:{ "version": "<packages/sandbox/package.json version>", "repository": "decocms/studio/studio-sandbox", "files": ["apps/studio-sandbox-stg/values.yaml", "apps/studio-sandbox-prod/values.yaml"] }Mirrors
release-mesh.yaml's dispatch pattern — sameDEPLOY_REPO_TOKEN(decobot), no cross-repo write credential in this repo.Behavior / safety
packages/sandboxchanges that reuse the existing tag), via a newimage-existsjob output.DEPLOY_REPO_TOKENisn't set — the bump never reds a release.Testing
YAML parses; job graph
build-push → bump-deco-apps-cd. The dispatch itself only exercises on a real main merge (needs the org secret). Anchor + files verified against the current deco-apps-cdstudio-sandbox-{stg,prod}/values.yaml.🤖 Generated with Claude Code
Summary by cubic
Automates rollout of new
studio-sandboximages by auto-bumping the tag indeco-apps-cdafter a successful image release. This removes manual values edits and keeps staging and prod aligned.bump-deco-apps-cdjob inrelease-studio-sandbox.yamlto dispatchimage-bumptodecocms/deco-apps-cdwith the new version and stg/prod values files.DEPLOY_REPO_TOKENis not set.Written for commit 5a2a7f5. Summary will update on new commits.