mirrors/semver
0
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2025-08-26 07:45:30 +00:00
Code

Omit build metadata from precedence rules

Browse Source 
Looks like a big change, but all I did was remove Build metadata from
the precedence rules.
This commit is contained in:
Haacked 2013-03-13 14:36:15 -07:00
parent 13aaadaadb
commit 5114f8543a
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
semver.md
View File

@ -87,14 +87,14 @@ precedence. Thus two packages with the same version, but different build
metadata are considered to be the same version.
1. Precedence MUST be calculated by separating the version into major, minor,
patch, pre-release, and build identifiers in that order. Major, minor, and
patch versions are always compared numerically. Pre-release precedence MUST be
determined by comparing each dot separated identifier as follows: identifiers
consisting of only digits are compared numerically and identifiers with
letters or hyphens are compared lexically in ASCII sort order. Numeric
identifiers always have lower precedence than non-numeric identifiers.
Example: 1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-beta.2 < 1.0.0-beta.11 <
1.0.0-rc.1 < 1.0.0.
patch and pre-release identifiers in that order (Build metadata does not figure
into precedence). Major, minor, and patch versions are always compared
numerically. Pre-release precedence MUST be determined by comparing each dot
separated identifier as follows: identifiers consisting of only digits are
compared numerically and identifiers with letters or hyphens are compared
lexically in ASCII sort order. Numeric identifiers always have lower precedence
than non-numeric identifiers. Example: 1.0.0-alpha < 1.0.0-alpha.1 <
1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.
Why Use Semantic Versioning?
----------------------------