Skip to content

chore(release): require explicit version confirmation before dispatch #320

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dean0x merged 1 commit into from
Sep 1, 2026
Merged

chore(release): require explicit version confirmation before dispatch #320

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .release/RELEASE-FLOW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,14 @@ Learned by `/release` on 2026-08-23 from: `package.json`, `.github/workflows/rel

## Version Strategy

- `semver-auto`: derive bump from conventional commits since last tag (`!`/BREAKING → major)
- `semver-auto`: derive a PROPOSED bump from conventional commits since last tag
(`!`/BREAKING → major). ALWAYS confirm the resulting version with the user before
dispatch, even when derivation is unambiguous (user directive, 2026-09-02) — present
the version explicitly, not just folded into the release-plan summary.
Also scan squash-commit BODIES for breaking-change sections (`## Breaking Changes`) —
PR templates document them there without the `!` marker; confirm major-vs-minor with
the user when found (2.1.0 shipped such changes as a minor by explicit user choice)
PR templates document them there without the `!` marker; a section stating "None" is
a negative declaration, not a breaking change (2.1.0 shipped real breaking changes as
a minor by explicit user choice; 2.4.0 resolved two "None" sections as minor)
- Tag format: `vX.Y.Z` (annotated). Release title: `vX.Y.Z`. No `v` prefix in CI input.
- Branching model: main-only, squash merges, no version PRs. CI bot commits directly to main
(ruleset bypass). `.devflow/conventions.md` absent — heuristics above learned from history.
Expand Down