ci: automated release, gated on CI passing on main - #2
Merged
Conversation
No release has been cut yet, and auto-publishing on every merge to main is premature. Switch the Release workflow from a push trigger to manual workflow_dispatch so releases are cut deliberately from the Actions tab. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018JWDajbftveEqqZWcrFH5n
Replace the manual workflow_dispatch trigger with a workflow_run trigger so the Release workflow runs automatically after CI succeeds on main, and never when CI is red. This restores the standard changesets flow (merge a changeset -> "Version Packages" PR -> merge to publish) while ensuring a broken main cannot publish. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018JWDajbftveEqqZWcrFH5n
karngyan
changed the title
Remove the premature changeset so merging does not auto-open a Version Packages PR. A release changeset will be added when we're ready to ship. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018JWDajbftveEqqZWcrFH5n
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
2 participants
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.
Why
Keep the ergonomic changesets flow (no manual button), but make sure a red
maincan never publish.How the release flow works now
pnpm changeset) and merge tomain.main. Only if it succeeds, the Release workflow fires (viaworkflow_run) and opens/updates a "Version Packages" PR.You never click "Run workflow" — you just merge PRs. Publishing is gated behind merging the Version Packages PR and CI being green.
What changed
fetch-depth: 0added so changesets can read full history for the changelog.~/.npmrcauth (from the earlier CI work) carried over.Notes
NPM_TOKENsecret. Until it's set, the Version-PR automation works but a publish attempt fails — so nothing ships early by accident.main(run on merge commit79be0ed).workflow_dispatchtrigger per the chosen "automated only" approach; easy to add later if you ever want a manual escape hatch.🤖 Generated with Claude Code
https://claude.ai/code/session_018JWDajbftveEqqZWcrFH5n