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

Merge 8e7fba3999 into d58db16863

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

4
semver.md
View File

@ -31,7 +31,7 @@ specified too loosely, you will inevitably be bitten by version promiscuity
Dependency hell is where you are when version lock and/or version promiscuity
prevent you from easily and safely moving your project forward.
As a solution to this problem, we propose a simple set of rules and
SemVer addresses this with a simple set of rules and
requirements that dictate how version numbers are assigned and incremented.
These rules are based on but not necessarily limited to pre-existing
widespread common practices in use in both closed and open-source software.
@ -44,7 +44,7 @@ affecting the API increment the patch version, backward compatible API
additions/changes increment the minor version, and backward incompatible API
changes increment the major version.
We call this system "Semantic Versioning." Under this scheme, version numbers
Under this scheme, version numbers
and the way they change convey meaning about the underlying code and what has
been modified from one version to the next.