Git & Version Control
Semantic Version Bumper
Enter current version and change type to compute the next semantic version number with pre-release and build metadata options.
No data is transmitted — everything runs locallyTool
Example — Version 2.4.7 bumped for a minor feature release in a normal semver workflow.
Current version
2.4.7
Change type
minor
new feature
Next version
2.5.0
npm tag command
npm version minor
bumps and creates git tag
About this tool
Semantic Version Bumper
The Semantic Version Bumper computes next version from current version and change type, covering major/minor/patch bumps, pre-release identifiers, and conventional commit mapping.
• Calculate the next version number before cutting a release
• Determine whether a change requires a major, minor, or patch bump
• Generate pre-release version strings for alpha/beta/rc releases
• Verify conventional commit type maps to the correct semver component
Affiliate disclosure
Credential and secrets management for teams. 1Password provides enterprise password management and secrets infrastructure for development teams.
View release credentials with 1Password
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The Semantic Version Bumper computes next version from current version and change type, covering major/minor/patch bumps, pre-release identifiers, and conventional commit mapping.
What affects the result most?
Semantic versioning: MAJOR.MINOR.PATCH — breaking.feature.fix. Pre-release: 1.0.0-alpha.1, 1.0.0-beta.2, 1.0.0-rc.1 — lower precedence than release. Build metadata: 1.0.0+build.123 — ignored for precedence, used for traceability.
How should I use the result?
The calculation is deterministic — the same inputs always produce the same output — so the most useful workflow is to vary one input at a time and see which factor moves the result most. That tells you where to focus your attention before committing to a decision.
Related tools