ci(release): propose-release becomes a manual dispatch - #46
Closed
using-system wants to merge 1 commit into
Closed
Conversation
Pushes to main no longer open/update the release PR - proposing a release is now Run workflow -> mode: propose. The push trigger stays for the tag-and-release chain (merge of a chore(release) PR), and the former bootstrap path is preserved as mode: publish-current. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
Folded into #45 per maintainer preference. |
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.
What
The release workflow's
propose-releasejob no longer fires on every push to main — it runs only via Run workflow → mode: propose (gh workflow run release.yml -f mode=propose). The push trigger remains solely for thetag-and-releasechain (merging achore(release)PR still tags/publishes automatically), and the old bootstrap path is preserved as mode: publish-current.Why
Every merge (docs, ci, chore included) was opening/updating a release PR — releasing becomes a deliberate act, and the noise stops.
Notes
🤖 Generated with Claude Code