Semver Compare
Compare two semantic version strings and identify breaking changes
About Semver Compare
Compares two version numbers in MAJOR.MINOR.PATCH form, tells you which one is newer and labels the difference as a major, minor or patch change, with both versions split into their parts in a table. The label follows the first number that differs, so going from 0.1.0 to 0.2.0 counts as minor even though SemVer allows breaking changes before 1.0.0. Handy for checking dependency upgrades and release tags.
Category: API.
Frequently asked questions
What is semantic versioning?
▾
A versioning scheme with the format MAJOR.MINOR.PATCH. MAJOR increments on breaking changes, MINOR on backwards-compatible new features, PATCH on backwards-compatible bug fixes.
Is 1.0.0 greater than 0.9.9?
▾
Yes. Each part is compared numerically left to right: 1 > 0 in the MAJOR position, so 1.0.0 is the higher version regardless of MINOR or PATCH values.
Which version formats does the tool accept?
▾
Three dot-separated numbers such as 1.4.2, optionally preceded by a lowercase v. Two-part versions like 1.4, an uppercase V and range syntax such as ^1.4.0 or ~1.4 are rejected as invalid.
How are pre-release versions like 1.0.0-beta.1 compared?
▾
Only the MAJOR.MINOR.PATCH numbers are compared; any pre-release tag or build metadata after them is ignored. As a result, 1.0.0-beta.1 and 1.0.0 are reported as equal, even though SemVer ranks the pre-release lower.