Semantic Version Bumper
Preview semver bumps before tagging a release.
Preview a semver bump
Semantic versioning encodes intent — major for breaking changes, minor for features, patch for fixes — but it is easy to bump the wrong part before tagging. This tool previews what a major, minor, or patch bump does to a version so you tag deliberately.
Seeing the resulting version before you cut a release avoids the confusion of an accidental major bump or a skipped number. Enter the current version, pick the change type, and copy the correct next version for your tag or changelog.
Bumping the right part
Major signals a breaking change, minor a feature, and patch a fix, so mixing them up misleads everyone downstream. The bump is computed in your browser.
Frequently asked questions
When should I bump major, minor, or patch?
Major for breaking changes, minor for new backward-compatible features, and patch for backward-compatible bug fixes.
What happens to the lower numbers when I bump?
They reset to zero. Bumping 1.4.2 to minor gives 1.5.0, and to major gives 2.0.0.
What does the pre-release option produce?
The next patch version with an -rc.1 tag, like 1.4.3-rc.1, for release candidates.
Related tools
Practical utilities for everyday web development work.