Semantic Version Compare
Parse and compare two Semantic Versions using SemVer 2.0.0 precedence rules.
How to use
- Enter Version A and Version B in SemVer format and run.
Capabilities and scope
The dedicated runner validates X.Y.Z, prerelease, and build metadata and applies numeric-versus-string prerelease ordering correctly.
How it works
Major, minor, and patch are compared first; prerelease identifiers follow SemVer ordering, while build metadata is ignored for precedence.
Example
1.0.0-rc.1 is lower precedence than 1.0.0.
Useful for
- Compare package versions according to SemVer precedence
Before you use it
- Version ranges such as ^1.2, loose versions, and npm range resolution are not supported; two complete versions are required.
Standards and references
Frequently asked questions
Does different +build metadata change precedence?
No. SemVer explicitly ignores build metadata for precedence.