Repository navigation
fix(ci): require manual dispatch to prepare a release - #208
Merged
Merged
Conversation
The Release workflow auto-opened a release/vX.Y.Z PR against main whenever CI succeeded on develop and a pending changeset existed, treating every green develop merge as an implicit release decision. workflow_run no longer listens on develop. Preparing a release is now a workflow_dispatch action a human triggers explicitly; the develop-side checks (changeset present, no open release PR, develop contains main's history) run inside that dispatch instead of inside an automatic CI-completion handler. Tagging a merged release PR on main stays automatic — that step follows an explicit human merge, not a develop push. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014oGzg7BoLAKHRuVjbS8uuC
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Contributor
Dependency Blast RadiusBase ref: Touched packages: none Impacted packages: none Package test signal: none flowchart LR
p_No_package_changes_detected["No package changes detected"]
|
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.
What
Removes the automatic develop-merge-triggers-a-release-PR behavior from the Release workflow.
Files: ~1
Why
The Release workflow auto-opened a
release/vX.Y.ZPR againstmainwhenever CI succeeded ondevelopand a pending changeset existed — treating every green develop merge as an implicit release decision. Releasing is now a deliberate action:workflow_dispatchon the Release workflow. Tagging a merged release PR onmainstays automatic, since that step follows an explicit human merge rather than a develop push.Testing
Verified: an in-flight Release run queued under the old trigger (develop CI completion) was cancelled before it opened a release PR;
workflow_runno longer listsdevelopin itsbranchesfilter;plan's detect script now branches ongithub.event_name == 'workflow_dispatch'for the prepare path and only handlesmainfor the tag path.Risks
Low — workflow-only change, no application code touched. A release can no longer be prepared by pushing to develop; it requires
gh workflow run release.yml(or the Actions UI "Run workflow" button) from a repo maintainer.Links
Checklist
An automation that releases on your behalf every time you merge is a standing debit order on your changelog — this cancels it and puts a signature back on the withdrawal.
🤖 Generated with Claude Code
https://claude.ai/code/session_014oGzg7BoLAKHRuVjbS8uuC