mirrors/semver
0
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2025-08-26 07:45:30 +00:00
Code

Reword scenario of accidental breaking changes

Browse Source 
Alternate proposal to #93. This fixes #38
This commit is contained in:
Haacked 2013-05-31 16:53:15 -07:00
parent 7a8bae9101
commit ff4fb481f6
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
semver.md
View File

@ -194,7 +194,7 @@ modification depends on whether you updated your dependencies in order to fix
a bug or introduce new functionality. I would usually expect additional code a bug or introduce new functionality. I would usually expect additional code
for the latter instance, in which case it's obviously a minor level increment. for the latter instance, in which case it's obviously a minor level increment.
### What should I do if the bug that is being fixed returns the code to being compliant with the public API (i.e. the code was incorrectly out of sync with the public API documentation)? ### 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 Use your best judgment. If you have a huge audience that will be drastically
impacted by changing the behavior back to what the public API intended, then impacted by changing the behavior back to what the public API intended, then