From 8e95cdbea80d93ff3ade5881e17ea966bc997134 Mon Sep 17 00:00:00 2001 From: Tom Preston-Werner Date: Sat, 19 Nov 2011 12:49:38 -0800 Subject: [PATCH] Use . instead of ~ as pre-release part separator. I realized that there is no point in using an exotic tilde when a dot will do just fine. In addition to being simpler and less weird, this change also means that you can tag these versions in Git, since ~ is invalid in Git tag names. --- semver.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/semver.md b/semver.md index ca49b6a..2abaa0c 100644 --- a/semver.md +++ b/semver.md @@ -52,18 +52,18 @@ version MUST be reset to zero. When a minor version number is incremented, the patch version MUST be reset to zero. For instance: 1.1.3 -> 2.0.0 and 2.1.7 -> 2.2.0. -1. A pre-release version number MAY be denoted by appending a dash and a -qualifying string immediately following the patch version. The qualifying -string is comprised of a mandatory identifier and an optional sequence number. -If the sequence number is used, it MUST be separated from the identifier by a -tilde. Identifiers MUST be comprised of only alphanumerics plus dash -[0-9A-Za-z-]. Sequence numbers MUST be comprised of only digits [0-9]. -Pre-release versions satisfy but have a lower precedence than the associated -normal version. Precedence SHOULD be determined by lexicographic ASCII sort -order of the identifier followed by numeric sort order of the sequence number. -If the sequence number is absent, it MUST be considered to be zero. For -example: 1.0.0-alpha < 1.0.0-alpha~1 < 1.0.0-beta~2 < 1.0.0-beta~11 < -1.0.0-rc~1 < 1.0.0. +1. A pre-release version MAY be denoted by appending a dash and a qualifying +string immediately following the patch version. The qualifying string is +comprised of a mandatory identifier and an optional sequence number. If the +sequence number is used, it MUST be separated from the identifier by a period. +Identifiers MUST be comprised of only alphanumerics plus dash [0-9A-Za-z-]. +Sequence numbers MUST be comprised of only digits [0-9]. Pre-release versions +satisfy but have a lower precedence than the associated normal version. +Precedence SHOULD be determined by lexicographic ASCII sort order of the +identifier followed by numeric sort order of the sequence number. If the +sequence number is absent, it MUST be considered to be zero. For example: +1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < +1.0.0. 1. Once a versioned package has been released, the contents of that version MUST NOT be modified. Any modifications must be released as a new version.