Skip to content

Version rules ​

CommitBump
feat!:, fix(x)!:, BREAKING CHANGE:major
feat:minor
fix:patch
everything elsenone
  • Before 1.0.0 a breaking change only bumps the minor version (bump-minor-pre-major, default true).
  • Without any tag the first release is calculated from 0.0.0 (feat → 0.1.0, fix → 0.0.1), unless initial-version is set.
  • Tags are v1.2.3; packages with a component use <component>-v1.2.3.
  • Only commits touching a package's path count for that package.
  • Reverted commits do not count: a Revert "feat: a" commit (or git's This reverts commit <sha> line) cancels the original commit since the last release. If nothing else is releasable, an open release merge request is closed. Both commits are also left out of the changelog.

Examples ​

Last tagCommits sinceNext versionWhy
v1.2.3fix: a1.2.4patch
v1.2.3fix: a, feat: b1.3.0highest bump wins
v1.2.3feat!: c2.0.0breaking change
v0.4.0feat!: c0.5.0bump-minor-pre-major
v0.4.0feat!: c with bump-minor-pre-major: false1.0.0breaking change bumps major
nonefeat: a0.1.0computed from 0.0.0
v1.2.3docs: a, chore: bnonenothing releasable

Use RELWOLF_RELEASE_AS to override the computed version.

Developed by lupiqlupiq