Merge pull request #150 from omniauth/security-versioning-policy

chore: Clarify versioning policy for security updates
omniauth · Feb 1, 2018 · 2234db9 · 2234db9
2 parents f0deffe + 3dcb5cd
commit 2234db9
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/README.md b/README.md
@@ -23,7 +23,7 @@ https://github.com/omniauth/omniauth-saml
 
 ## Versioning
 
-We tag and release gems according to the [Semantic Versioning](http://semver.org/) principle.
+We tag and release gems according to the [Semantic Versioning](http://semver.org/) principle. In addition to the guidelines of Semantic Versioning, we follow a further guideline that otherwise backwards-compatible dependency upgrades for security reasons should generally be cause for a MINOR version upgrade as opposed to a PATCH version upgrade. Backwards-incompatible dependency upgrades for security reasons should still result in a MAJOR version upgrade for this library.
 
 ## Usage