0
0
mirror of https://github.com/semver/semver.git synced 2025-08-26 15:55:30 +00:00

Omit build metadata from precedence rules

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

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