mirrors/semver
0
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2025-08-22 22:08:33 +00:00
Code

Merge 19e0e0ae37 into d58db16863

Browse Source
This commit is contained in:
Matthijs Kooijman 2025-06-23 19:31:21 +09:00 committed by GitHub
commit 8572430058
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
semver.md
View File

@ -90,9 +90,11 @@ incompatible changes are introduced to the public API. It MAY also include minor
and patch level changes. Patch and minor versions MUST be reset to 0 when major and patch level changes. Patch and minor versions MUST be reset to 0 when major
version is incremented. version is incremented.
1. A pre-release version MAY be denoted by appending a hyphen and a 1. A pre-release version MAY be denoted by appending a hyphen followed
series of dot separated identifiers immediately following the patch by one or more identifiers. The hyphen immediately follows the patch
version. Identifiers MUST comprise only ASCII alphanumerics and hyphens 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 [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST
NOT include leading zeroes. Pre-release versions have a lower NOT include leading zeroes. Pre-release versions have a lower
precedence than the associated normal version. A pre-release version precedence than the associated normal version. A pre-release version
@ -101,8 +103,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, 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.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 1. Build metadata MAY be denoted by appending a plus sign followed by one
separated identifiers immediately following the patch or pre-release version. 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 comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-].
Identifiers MUST NOT be empty. Build metadata MUST be ignored when determining Identifiers MUST NOT be empty. Build metadata MUST be ignored when determining
version precedence. Thus two versions that differ only in the build metadata, version precedence. Thus two versions that differ only in the build metadata,