From d7aaef6709ff4c4e621a7ccfaf405c4b0aea9b36 Mon Sep 17 00:00:00 2001 From: Matthijs Kooijman Date: Thu, 10 Mar 2016 13:44:10 +0100 Subject: [PATCH 1/2] Slightly clarify the build metadata section Multiple people (#291, #249, #230, #293) have missed the fact that the build metadata can contain multiple *dot-separated* identifers, and were confused enough to report a bug about the dots present in one of the examples. This attempts to make it more obvious that multiple identifiers might be used. This closes #293. --- semver.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/semver.md b/semver.md index ac37a19..e5ded4f 100644 --- a/semver.md +++ b/semver.md @@ -102,8 +102,10 @@ intended compatibility requirements as denoted by its 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, 1.0.0-x-y-z.--. -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. +1. Build metadata MAY be denoted by appending a plus sign followed by one +or more identifiers. The plus sign immediately follows the patch or +pre-release version and is followed by the first identifier. If multiple +identifiers are used, they are separated with dots. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata MUST be ignored when determining version precedence. Thus two versions that differ only in the build metadata, From 19e0e0ae377aaaca16c33183ed220ffb868bd713 Mon Sep 17 00:00:00 2001 From: Matthijs Kooijman Date: Mon, 14 Mar 2016 08:25:13 +0100 Subject: [PATCH 2/2] Also clarify the pre-release version description --- semver.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/semver.md b/semver.md index e5ded4f..06c0e57 100644 --- a/semver.md +++ b/semver.md @@ -91,9 +91,11 @@ incompatible changes are introduced to the public API. It MAY also include minor and patch level changes. Patch and minor version MUST be reset to 0 when major version is incremented. -1. A pre-release version MAY be denoted by appending a hyphen and a -series of dot separated identifiers immediately following the patch -version. Identifiers MUST comprise only ASCII alphanumerics and hyphens +1. A pre-release version MAY be denoted by appending a hyphen followed +by one or more identifiers. The hyphen immediately follows the patch +version and is followed by the first identifier. If multiple identifiers +are used, they are separated with dots. +Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version