From dd92b6460ac8fc2e626f47d6f3498d17cefae54c Mon Sep 17 00:00:00 2001 From: Joseph Donahue Date: Wed, 22 Jan 2020 15:40:34 -0800 Subject: [PATCH] Hyphen should be hyphens in the pre-release clause (#466) * Hyphen should be hyphens in the pre-release clause Fix for #465 How many hypens are you allowed in the prerelease tag. * Added pluralization of hyphen in prerelease. Added pluralization of hyphen in prerelease as well as additional examples in prerelease and build meta. --- semver.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/semver.md b/semver.md index be210b3..04cca5b 100644 --- a/semver.md +++ b/semver.md @@ -93,22 +93,22 @@ 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 hyphen +version. 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 indicates that the version is unstable and might not satisfy the 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.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. -Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. +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, have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, -1.0.0-beta+exp.sha.5114f85. +1.0.0-beta+exp.sha.5114f85, 1.0.0+21AF26D3----117B344092BD. 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