SemVer bump and compare
Parse a version, bump major / minor / patch / prerelease, or compare two versions. Nothing is uploaded.
Ready
How it works
This page follows SemVer 2.0.0: MAJOR.MINOR.PATCH, optional -prerelease, optional +build. A leading v is stripped. Build metadata is ignored in comparison.
Precedence: major, then minor, then patch, then prerelease identifiers (numeric vs non-numeric). A release beats a prerelease of the same core: 1.0.0 > 1.0.0-rc.1.
^1.2.3 means compatible with 1.x (≥1.2.3 <2.0.0). ~1.2.3 means approximately 1.2.x (≥1.2.3 <1.3.0). Those notes are for reading npm ranges; this tool bumps and compares concrete versions.
Examples
1.2.3 patch → 1.2.4 1.2.3 minor → 1.3.0 1.2.3 major → 2.0.0 1.2.3-rc.1 prerelease → 1.2.3-rc.2 0.4.1 minor → 0.5.0 (0.x still bumps that segment)
FAQ
Does 0.x mean anything special here? SemVer treats 0.y.z as initial development. This page still applies the same bump rules; it does not change caret range meaning.
What happens to prerelease on a major bump? It is dropped. 1.2.3-rc.1 major → 2.0.0.
Is +build compared? No. 1.0.0+aaa equals 1.0.0+bbb.
Can I paste a range like ^1.2.3? No. Enter a single version. Ranges are documented only.
Does this leave the browser? No. Parsing is local JavaScript.