Semantic Version Checker
Check semantic versions, sort a list, bump a version, or test versions against an npm-style range such as ^1.2.3 or >=2.0.0 <3.
How to check semantic versions
Paste your versions
One per line, such as 1.2.3 or 2.0.0-beta.1.
Add a range
For example ^1.2.0 or >=2.0.0 <3. Each version is tested against it.
Read the table
See which are valid, which match, their order and an optional bump.
Worked example
This is what Semantic Version Checker gives for its own sample values. Open the tool above and change anything to try your own.
Versions (one per line)
1.2.3 1.10.0 2.0.0-beta.1 1.2.3-rc.1 v3.0.0 1.2
- Test against a range (optional)
- ^1.2.0
- Bump each version
- Do not bump
Sorted, oldest first
1.2.3-rc.1 1.2.3 1.10.0 2.0.0-beta.1 v3.0.0
| Version | Valid | Matches range | Order (oldest first) |
|---|---|---|---|
| 1.2.3 | valid | yes | 2 |
| 1.10.0 | valid | yes | 3 |
| 2.0.0-beta.1 | valid | no | 4 |
| 1.2.3-rc.1 | valid | no | 1 |
| v3.0.0 | valid | no | 5 |
About Semantic Version Checker
Validate semantic versions, sort a list from oldest to newest using the real precedence rules, test versions against an npm-style range, and bump a version by major, minor, patch or prerelease.
FAQs
Which range syntax is supported?
Caret, tilde, comparison operators, x-ranges such as 1.x, hyphen ranges and || for alternatives.
Why does a prerelease not match ^1.0.0?
As in npm, a prerelease only matches a range that mentions a prerelease of the same version.
Is a leading v allowed?
Yes. v1.2.3 is read as 1.2.3.