Decide the correct SemVer version bump for the next release
Decide the correct Semantic Versioning bump when preparing a release.
| Change in this release | Bump | Example |
|---|---|---|
Any BREAKING CHANGE footer or ! commit | MAJOR | 1.2.3 → 2.0.0 |
At least one feat commit | MINOR | 1.2.3 → 1.3.0 |
Only fix, perf, revert commits | PATCH | 1.2.3 → 1.2.1 |
Only docs, chore, ci, build, style, , |
refactortest| PATCH |
1.2.3 → 1.2.1 |
Rule precedence: MAJOR > MINOR > PATCH. A single breaking change overrides everything else.
Version bumps are applied automatically by the Create Release Branch + PR GitHub Actions workflow.
You only need to decide the version and enter it when triggering the workflow.
Steps:
develop since the last release tagActions → Create Release Branch + PR1.3.0) — no v prefix in the input fieldThe workflow will:
version in package.jsonCHANGELOG.md section headerPre-release versions (1.3.0-alpha.1) are created automatically by the pre-release workflow for PRs to main. Do not set pre-release suffixes manually.
During initial development (before 1.0.0), breaking changes may bump MINOR instead of MAJOR. Once 1.0.0 is tagged, follow the rules strictly.