SemVer Precedence Comparison
Compare two Semantic Versioning 2.0.0 identifiers and see which one has higher precedence and which identifier decides it. All computation happens locally; nothing you type is uploaded or stored.
Switching languages or leaving the page discards your draft. A result is only valid for the current input snapshot; editing the input immediately invalidates the old result and its download.
Precedence and deciding identifier
| Field | Left version | Right version | Note |
|---|
Input limits
- Each version is at most 256 characters. No trimming: leading or trailing spaces are rejected.
- Format is
major.minor.patch, with optional-prereleaseand+build; novprefix. - Each core field is at most 32 digits, with no leading zeros (except 0 itself).
- Prerelease and build each have at most 16 identifiers, each at most 32 characters, using only
0-9 A-Z a-z -. - A purely numeric prerelease identifier must not have leading zeros; build identifiers may.
- Build metadata does not affect precedence.
Frequently asked questions
Does rc.10 outrank rc.2?
With the same prefix, numeric 10 has higher precedence than 2.
Does +build.2 outrank +build.1?
Build metadata does not affect precedence.