From e692c2f11347dea1442b3e5d831a9336970407d7 Mon Sep 17 00:00:00 2001 From: isaacs Date: Thu, 6 Jun 2013 07:52:53 -0700 Subject: [PATCH 1/3] Section 10: Clarify language around build metadata precedence They're not the 'same version', necessarily, they're the same precedence --- semver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/semver.md b/semver.md index f49c477..3f1e709 100644 --- a/semver.md +++ b/semver.md @@ -88,8 +88,8 @@ associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, separated identifiers immediately following the patch or pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Build metadata SHOULD be ignored when determining version precedence. Thus two -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, +packages with the same version, but different build metadata, are +the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85. 1. Precedence refers to how versions are compared to each other when ordered. From 3071b5d2d59f4c768427ee3f6ec2ea16bdea4b2c Mon Sep 17 00:00:00 2001 From: Haacked Date: Sun, 9 Jun 2013 21:03:46 -0700 Subject: [PATCH 2/3] Clarify non-empty build metadata - 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. --- semver.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/semver.md b/semver.md index 3f1e709..f5de2e8 100644 --- a/semver.md +++ b/semver.md @@ -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 separated identifiers immediately following the patch or pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. -Build metadata SHOULD be ignored when determining version precedence. Thus two -packages with the same version, but different build metadata, are -the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, -1.0.0-beta+exp.sha.5114f85. +Identifiers MUST NOT be empty. Build metadata SHOULD be ignored when determining +version precedence. Thus two packages with the same version, but different build +metadata, have the same precedence. Examples: 1.0.0-alpha+001, +1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85. 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 From ec887c3b97e5eb36b17d47ce02925fa35b436ce3 Mon Sep 17 00:00:00 2001 From: Haacked Date: Mon, 10 Jun 2013 09:08:07 -0700 Subject: [PATCH 3/3] Be more precise about version precedence --- semver.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/semver.md b/semver.md index f5de2e8..0a43836 100644 --- a/semver.md +++ b/semver.md @@ -88,9 +88,9 @@ associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, separated identifiers immediately following the patch or pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata SHOULD be ignored when determining -version precedence. Thus two packages with the same version, but different build -metadata, have the same precedence. Examples: 1.0.0-alpha+001, -1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85. +version precedence. Thus two versions that differ only in the build metadata, +have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, +1.0.0-beta+exp.sha.5114f85. 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