chore(release): require explicit version confirmation before dispatch - #320
Merged
Conversation
Record the user directive from the v2.4.0 release in the learned release config: semver-auto now derives a PROPOSED bump only, and the resulting version must always be confirmed explicitly with the user before dispatching, even when derivation is unambiguous. Also clarify that a squash-body "## Breaking Changes: None" section is a negative declaration, not a breaking change requiring major-vs-minor discussion.
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.
Summary
Records a user directive in the learned release config (
.release/RELEASE-FLOW.md): the version derived by semver-auto is a proposal — it must always be confirmed explicitly with the user before dispatching the release workflow, even when derivation is unambiguous.Changes
## Breaking Changessection stating "None" is a negative declaration, not a breaking change (2.4.0 resolved two such sections as minor)Breaking Changes
None.
Testing
Config prose only — consumed by the
/releaseorchestrator; no code paths affected.