Skip to content

chore(release): cap auto-bumps at minor to avoid accidental majors #1608

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

Open
MuncleUscles wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(release): cap auto-bumps at minor to avoid accidental majors #1608

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
12 changes: 12 additions & 0 deletions release.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,19 @@ module.exports = {
"@semantic-release/commit-analyzer",
{
"preset": "conventionalcommits",
// The first rule caps commits with a BREAKING CHANGE footer or `!:`
// marker at `minor`. Without it, semantic-release's built-in default
// rule `{ breaking: true, release: 'major' }` kicks in and auto-ships
// a major release the moment any commit body contains the words
// "BREAKING CHANGE". That's almost never what we want on 0.x — one
// stray commit would jump us straight to 1.0.0. Run semantic-release
// with an explicit `--release major` override for genuine major bumps.
//
// User rules are evaluated before the defaults; defaults only apply
// when no user rule matches. So capturing `breaking: true` here
// prevents the default major rule from being consulted at all.
"releaseRules": [
{ "breaking": true, "release": "minor" },
{ "type": "feat", "release": "minor" },
{ "type": "*", "release": "patch" },
],
Expand Down
Loading