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 8d19c8a91f into d58db16863

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

13
semver.md
View File

@ -301,6 +301,19 @@ modification depends on whether you updated your dependencies in order to fix
a bug or introduce new functionality. We would usually expect additional code
for the latter instance, in which case it's obviously a minor level increment.
#### Special note for JVM or similar environments
In such environments where only one version of a library could
be present in a running system, the transitive dependencies effectively become
part of the public library interface and thus the version of the user library SHOULD be
incremented to the same degree as the version of the transitive dependency:
- for MAJOR change in transitive dependency we SHOULD increment MAJOR part of our version,
- for MINOR change in transitive dependency we SHOULD increment MINOR part of our version,
- for PATCH change in transitive dependency we SHOULD increment PATCH part of our version.
If a few dependencies are being changed, only the highest degree is required to be incremented.
(See also [the discussion](https://github.com/semver/semver/issues/341).)
### What if I inadvertently alter the public API in a way that is not compliant with the version number change (i.e. the code incorrectly introduces a major breaking change in a patch release)?
Use your best judgment. If you have a huge audience that will be drastically