Dev
Generator für Semantic-Version-Bumps
A semantic version bump generator calculates the next version number for a major, minor, or patch release, following the semver rules every package and API depends on. Semantic versioning encodes meaning into three numbers — major for breaking changes, minor for new backward-compatible features, and patch for fixes — and bumping the wrong field, or forgetting to reset the lower ones, causes real confusion downstream. This tool parses your current version and applies the correct bump, resetting the fields that semver requires. Enter a version, pick the type of change, and copy the result. It is ideal for releasing libraries, tagging Git versions, and updating a package manifest. Remember the core rule: a major bump resets minor and patch to zero, a minor bump resets patch, and a patch bump increments the last number — getting this right keeps consumers safe.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Enter your current version.
- Choose major, minor, or patch.
- Click Generate to see the next version.
- Copy it into your tag or manifest.
Use Cases
- •Deciding the next version for a release
- •Tagging a Git release correctly
- •Updating a package.json version
- •Teaching semantic versioning rules
- •Avoiding version-bump mistakes
Tips
- →Major bumps signal breaking changes.
- →Reset lower fields on a higher bump.
- →Patch is for backward-compatible fixes.
- →Tag releases to match the version.
FAQ
what do major, minor, and patch mean
In semantic versioning, you bump major for breaking changes, minor for new backward-compatible features, and patch for backward-compatible bug fixes. The three numbers tell consumers at a glance how risky upgrading to your new version is.
why reset the lower numbers
Semver requires it: a major bump resets minor and patch to zero, and a minor bump resets patch. Resetting keeps the version sequence meaningful, so 2.0.0 clearly supersedes 1.9.7 rather than leaving a confusing trail of stale numbers.
what if my version has a pre-release tag
This tool focuses on the core major.minor.patch numbers. Pre-release and build metadata, like -beta.1 or +build, follow additional semver rules; handle those separately once you have settled the main version bump.
When should I bump the major version?
Bump MAJOR whenever you make a backwards-incompatible change — removing or renaming an API, changing behaviour existing users rely on, or anything that could break their code — signalling they must review before upgrading. The generator calculates the correct next version for a major bump (resetting minor and patch to zero), so your release follows semver's contract and downstream users can trust what an upgrade means.
How does semver work with automated release tools?
Tools like semantic-release read your commit messages (often Conventional Commits) to decide whether a change is a fix, feature, or breaking change, then bump the version automatically and generate a changelog. The generator mirrors that bump logic for major, minor, and patch, so you can sanity-check or prototype the versioning rules your pipeline will apply before wiring up full automation.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.