github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-03-08 23:12:02 -05:00
Code Issues 118 Packages Projects Releases 4 Wiki Activity

Merge pull request #975 from vaitkus/fix-style-issues

Browse Source
This commit is contained in:
Yuki Okushi
2025-06-23 19:31:18 +09:00
committed by GitHub
parent af8bf6cfbd ee4f1d2657
commit d58db16863
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
semver.md
View File

@@ -112,11 +112,11 @@ have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700,
1. Precedence refers to how versions are compared to each other when ordered.
1. Precedence MUST be calculated by separating the version into major,
minor, patch and pre-release identifiers in that order (Build metadata
minor, patch and pre-release identifiers in that order (build metadata
does not figure into precedence).
1. Precedence is determined by the first difference when comparing each of
these identifiers from left to right as follows: Major, minor, and patch
these identifiers from left to right as follows: major, minor, and patch
versions are always compared numerically.
Example: 1.0.0 < 2.0.0 < 2.1.0 < 2.1.1.
@@ -322,7 +322,7 @@ 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,
No, but use good judgment. A 255 character version string is probably an overkill,
for example. Also, specific systems may impose their own limits on the size of
the string.