From ff4fb481f63613f843750bd1f3093d83eb50faaa Mon Sep 17 00:00:00 2001 From: Haacked Date: Fri, 31 May 2013 16:53:15 -0700 Subject: [PATCH] Reword scenario of accidental breaking changes Alternate proposal to #93. This fixes #38 --- semver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/semver.md b/semver.md index 6509b48..281cb76 100644 --- a/semver.md +++ b/semver.md @@ -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 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 impacted by changing the behavior back to what the public API intended, then