Semantic version bump calculator
Paste the commits since your last release and get a suggestion for the next version. Free, no sign-in, and it runs in your browser.
The commits since your last release, one per line. Paste the output of git log --oneline --no-decorate. To include commit bodies, so that a BREAKING CHANGE footer is seen, use git log --format=%B v1.4.2..HEAD.
1.5.0
Suggestion: minor bump to 1.5.0
- Minorfeat: add pdf export (#142)
- Patchfix: oauth redirect loop (#139)
0 breaking, 1 features, 1 fixes, 3 not counted.
This tool runs in your browser. What you paste is not sent anywhere.
Then write the release notes
Once you know the version, ReleaseTale reads the commits and pull requests of the release and drafts the notes for your users and the entry for developers.
How the suggestion is worked out
The calculator follows Semantic Versioning 2.0.0 and reads your commits as Conventional Commits. The strongest change sets the suggested bump, and the lower numbers are reset to zero.
| Commit | Bump | Meaning |
|---|---|---|
any type with !, or BREAKING CHANGE: on its own line | Major | An incompatible change to the public API |
feat, deprecate | Minor | A new feature, or something marked for removal, without breaking users |
fix, perf, security, revert | Patch | A backward compatible bug fix (perf and security by convention) |
chore, docs, test, ci, build, style, refactor, merge commits | Not counted | Usually nothing a user can notice |
The result is a suggestion. Commit messages are written for maintainers and do not always say whether a change breaks users, so read the reasons the tool lists and change the number if you know something it does not.
After you pick the version
Write the changelog entry for it. Paste the same commits into the changelog generator for a first draft, and check the finished file with the CHANGELOG.md validator. For the reasoning behind the numbers, read Semantic Versioning and your changelog.
Frequently asked questions
How do I know which version number to bump?
Look at the changes since the last release. A breaking change to the public API raises the major number. A new backward compatible feature, or marking functionality as deprecated, raises the minor number. A backward compatible bug fix raises the patch number.
How does the calculator read my commits?
It reads Conventional Commits: feat raises the minor number, fix, perf, security and revert raise the patch number, any type followed by ! or a line that starts with BREAKING CHANGE: raises the major number, and deprecate raises the minor number. A BREAKING CHANGE footer must be on its own line, and git log --oneline leaves commit bodies out, so use git log --format=%B to include them. Everything else is not counted.
Is the result a decision?
No, it is a suggestion. Commit messages do not always say whether a change breaks users, so read the list and override the number when you know better.
What about versions before 1.0.0?
Semantic Versioning treats 0.y.z as initial development, where anything may change, so tools differ. This calculator raises the minor number for a breaking change. Some tools raise the patch number for a feature before 1.0.0, and some move a breaking change straight to 1.0.0. Follow the rule your project states.
Is my commit history sent to a server?
No. The calculation runs in your browser, so what you paste never leaves your machine.