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

Clarify non-empty build metadata

Browse Source 
- Build metadata identifiers MUST not be empty.
- Changed "are" to "have" when discussing version precedence. We usually
say a version HAS a precedence not that it IS a precedence.
This commit is contained in:
Haacked 2013-06-09 21:03:46 -07:00
parent e692c2f113
commit 3071b5d2d5
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
semver.md
View File

@ -87,10 +87,10 @@ associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1,
1. Build metadata 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 or pre-release version. separated identifiers immediately following the patch or pre-release version.
Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-].
Build metadata SHOULD be ignored when determining version precedence. Thus two Identifiers MUST NOT be empty. Build metadata SHOULD be ignored when determining
packages with the same version, but different build metadata, are version precedence. Thus two packages with the same version, but different build
the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, metadata, have the same precedence. Examples: 1.0.0-alpha+001,
1.0.0-beta+exp.sha.5114f85. 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85.
1. Precedence refers to how versions are compared to each other when ordered. 1. Precedence refers to how versions are compared to each other when ordered.
Precedence MUST be calculated by separating the version into major, minor, patch Precedence MUST be calculated by separating the version into major, minor, patch