Break a semantic version into its parts, see every bump from it, and sort a list in true semver order — which is neither string order nor number order.
1.4.2 → 1.5.0
Minor — a new feature, backwards compatible
2.0.01.5.01.4.32.0.0-beta.01.5.0-beta.01.4.3-beta.01.4.3-beta.0Semantic Version Inspector runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Semver ordering is neither string order nor number order, and both of the rules that make it different are easy to get wrong by hand. `1.10.0` comes after `1.9.0`, even though "1.10" sorts before "1.9" as text. And within a pre-release, numeric identifiers compare numerically while alphanumeric ones compare as text — so `alpha.2` is before `alpha.10`, which is the opposite of what string sorting gives you.
A pre-release always sorts below the release it precedes. `1.0.0-rc.1` is less than `1.0.0`, which surprises people who read the pre-release as "1.0.0 plus a bit". It is the reason a range of `^1.0.0` does not match a release candidate for 1.0.0.
Build metadata is ignored entirely for ordering. `1.0.0+build.1` and `1.0.0+build.2` are the same version as far as semver is concerned, and a registry will reject the second as a duplicate — which is a confusing error if you were using the metadata to distinguish builds.
Every bump from the current version is shown at once rather than one at a time, because the interesting question is usually which of them you want. The pre-release bumps in particular behave differently depending on whether you are already in a pre-release, and seeing all seven makes that obvious.
Before. A pre-release always sorts below the release it precedes — that is what makes it a pre-release. It is also why a ^1.0.0 range does not match 1.0.0-rc.1 unless pre-releases are explicitly included.
Because numeric pre-release identifiers compare numerically. If they were alphanumeric they would compare as text and alpha.10 would come first. Mixing the two in one series is how pre-release ordering becomes unpredictable.
Recording something about the build — a commit hash, a timestamp — without changing the version. It is ignored for ordering and for equality, so two versions differing only in metadata are the same version and a registry will reject the second as a duplicate.
Not as part of the version. Semver does not include it; git tags conventionally do. Both are accepted here and the v is stripped, which is what every tool that reads tags does.
That anything may change at any time. Semver makes no compatibility promise below 1.0.0, and range operators behave differently there — ^0.3.1 allows only patches where ^1.3.1 allows minors.