github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-03-11 17:48:09 -05:00
Code Issues 118 Packages Projects Releases 4 Wiki Activity

Merge pull request #96 from Tieske/master

Browse Source 
Replaces #30, pre-release versions are unstable
This commit is contained in:
Phil Haack
2013-05-31 16:46:32 -07:00
parent 72981408bd 586f185f7a
commit 7a8bae9101
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
semver.md
View File

@@ -79,7 +79,10 @@ version is incremented.
dot separated identifiers immediately following the patch version. Identifiers
MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Pre-release
versions satisfy but have a lower precedence than the 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.
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. 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.
@@ -210,6 +213,11 @@ in place. Before you completely remove the functionality in a new major release
there should be at least one minor release that contains the deprecation so
that users can smoothly transition to the new API.
### Does semver have a size limit on the version string?
No, but use good judgment. A 255 character version string is probably overkill,
for example. Also, specific systems may impose their own limits on the size of
the string.
About
-----