0
0
mirror of https://github.com/semver/semver.git synced 2025-08-28 16:55:29 +00:00

Merge pull request #107 from mojombo/clarify-prerelease

Section 9: Clarify pre-release definition
This commit is contained in:
Phil Haack 2013-06-10 16:48:06 -07:00
commit fed7399185

View File

@ -75,14 +75,15 @@ incompatible changes are introduced to the public API. It MAY include minor
and patch level changes. Patch and minor version MUST be reset to 0 when major and patch level changes. Patch and minor version MUST be reset to 0 when major
version is incremented. version is incremented.
1. A pre-release version MAY be denoted by appending a hyphen and a series of 1. A pre-release version MAY be denoted by appending a hyphen and a
dot separated identifiers immediately following the patch version. Identifiers series of dot separated identifiers immediately following the patch
MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphen
versions satisfy but have a lower precedence than the associated normal [0-9A-Za-z-]. Identifiers MUST NOT be empty. Pre-release versions have
version. A pre-release version indicates that the version is unstable and a lower precedence than the associated normal version. A pre-release
might not satisfy the intended compatibility requirements as denoted by its version indicates that the version is unstable and might not satisfy
associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, the intended compatibility requirements as denoted by its associated
1.0.0-0.3.7, 1.0.0-x.7.z.92. 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.
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.