Skip to content

Conversation

@sestinj
Copy link
Contributor

@sestinj sestinj commented Jan 26, 2026

Summary

  • Updates stable release workflow to publish both cn and cn-staging blueprints
  • Previously, cn-staging was only rebuilt when the template JSON files were modified, causing staging devboxes to run old CLI code after releases

Context

The cn-staging blueprint 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

  • Trigger a stable release and verify both blueprints are published successfully in the workflow logs
  • Create a new staging devbox and verify it has the latest CLI version

🤖 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

    • Always publish cn-staging on stable releases to prevent stale CLI in staging devboxes.
  • Refactors

    • Introduced a publish_blueprint helper to reuse logic and improve logging/error handling.

Written for commit 3fa46d8. Summary will update on new commits.

The cn-staging blueprint was not being rebuilt when CLI changes were
released, causing staging devboxes to run old code. This updates the
stable release workflow to publish both cn and cn-staging blueprints.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@sestinj sestinj requested a review from a team as a code owner January 26, 2026 08:25
@sestinj sestinj requested review from Patrick-Erichsen and removed request for a team January 26, 2026 08:25
@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Jan 26, 2026
@github-actions
Copy link

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

  • feat: add changelog generation support
  • fix: resolve login redirect issue
  • docs: update README with new instructions
  • chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

  • 📝 Automatic changelog generation
  • 🚀 Automated semantic versioning
  • 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

@github-actions
Copy link

github-actions bot commented Jan 26, 2026

✅ Review Complete

Code Review Summary

⚠️ Continue API authentication failed. Please check your CONTINUE_API_KEY.


Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@sestinj sestinj merged commit 1521f83 into main Jan 26, 2026
58 of 60 checks passed
@sestinj sestinj deleted the nate/publish-staging-blueprint branch January 26, 2026 09:00
@github-project-automation github-project-automation bot moved this from Todo to Done in Issues and PRs Jan 26, 2026
@github-actions github-actions bot locked and limited conversation to collaborators Jan 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

size:M This PR changes 30-99 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants