mirrors/semver
0
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2025-08-25 15:25:29 +00:00
Code

Merge pull request #77 from mojombo/build-metadata-identifier

Browse Source 
Build metadata identifier
This commit is contained in:
Phil Haack 2013-03-20 15:00:55 -07:00
commit eceeff12c5
1 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
semver.md
View File

@ -1,4 +1,4 @@
Semantic Versioning 2.0.0-rc.1 Semantic Versioning 2.0.0-rc.2
============================== ==============================
In the world of software management there exists a dread place called In the world of software management there exists a dread place called
@ -79,22 +79,23 @@ MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Pre-release
versions satisfy but have a lower precedence than the associated normal versions satisfy but have a lower precedence than the associated normal
version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92. version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92.
1. A build version MAY be denoted by appending a plus sign and a series of dot 1. Build metadata MAY be denoted by appending a plus sign and a series of dot
separated identifiers immediately following the patch version or pre-release separated identifiers immediately following the patch or pre-release version.
version. Identifiers MUST be comprised of only ASCII alphanumerics and hyphen Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-].
[0-9A-Za-z-]. Build versions satisfy and have a higher precedence than the Build metadata SHOULD be ignored when determining version precedence. Thus two
associated normal version. Examples: 1.0.0+build.1, 1.3.7+build.11.e0f985a. packages with the same version, but different build metadata are considered to
be the same version. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700,
1.0.0-beta+exp.sha.5114f85.
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 and build version into precedence). Major, minor, and patch versions are always compared
precedence MUST be determined by comparing each dot separated identifier as numerically. Pre-release precedence MUST be determined by comparing each dot
follows: identifiers consisting of only digits are compared numerically and separated identifier as follows: identifiers consisting of only digits are
identifiers with letters or hyphens are compared lexically in ASCII sort order. compared numerically and identifiers with letters or hyphens are compared
Numeric 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-rc.1+build.1 < 1.0.0 < 1.0.0+0.3.7 < 1.3.7+build < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.
1.3.7+build.2.b8f12d7 < 1.3.7+build.11.e0f985a.
Why Use Semantic Versioning? Why Use Semantic Versioning?
---------------------------- ----------------------------