From 5114f8543aba8ed1244f09bb2612a3ea5738df49 Mon Sep 17 00:00:00 2001 From: Haacked Date: Wed, 13 Mar 2013 14:36:15 -0700 Subject: [PATCH] Omit build metadata from precedence rules Looks like a big change, but all I did was remove Build metadata from the precedence rules. --- semver.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/semver.md b/semver.md index 257e329..5ecbeb2 100644 --- a/semver.md +++ b/semver.md @@ -87,14 +87,14 @@ precedence. Thus two packages with the same version, but different build metadata are considered to be the same version. 1. Precedence MUST be calculated by separating the version into major, minor, -patch, pre-release, and build identifiers in that order. Major, minor, and -patch versions are always compared numerically. Pre-release precedence MUST be -determined by comparing each dot separated identifier as follows: identifiers -consisting of only digits are compared numerically and identifiers with -letters or hyphens are compared lexically in ASCII sort order. Numeric -identifiers always have lower precedence than non-numeric identifiers. -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. +patch and pre-release identifiers in that order (Build metadata does not figure +into precedence). Major, minor, and patch versions are always compared +numerically. Pre-release precedence MUST be determined by comparing each dot +separated identifier as follows: identifiers consisting of only digits are +compared numerically and identifiers with letters or hyphens are compared +lexically in ASCII sort order. Numeric identifiers always have lower precedence +than non-numeric identifiers. 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. Why Use Semantic Versioning? ----------------------------