Publish cn-staging blueprint on stable release #9914
Merged
+40
−32
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
cnandcn-stagingblueprintscn-stagingwas only rebuilt when the template JSON files were modified, causing staging devboxes to run old CLI code after releasesContext
The
cn-stagingblueprint was not being updated when CLI releases were published, which meant staging devboxes were running outdated code even after a new version was deployed to npm.Test plan
🤖 Generated with Claude Code
Continue Tasks:▶️ 3 queued — View all
Summary by cubic
Publish both cn and cn-staging blueprints during the stable release. This ensures staging devboxes run the latest CLI after each release.
Bug Fixes
Refactors
Written for commit 3fa46d8. Summary will update on new commits.