Skip to content

Instantly share code, notes, and snippets.

@perlguy99

perlguy99/Semantic_Versioning.md

Last active December 13, 2019 15:28
Show Gist options
  • Save perlguy99/e01cfa054569257dd4bb2d9fc6148299 to your computer and use it in GitHub Desktop.
Save perlguy99/e01cfa054569257dd4bb2d9fc6148299 to your computer and use it in GitHub Desktop.
Download ZIP
Semantic Versioning
Raw
Semantic_Versioning.md

Semantic versioning (SemVer)

Example

If you look at a version like 1.5.3, then the 1 is considered the major number, the 5 is considered the minor number, and the 3 is considered the patch number.

If developers follow SemVer correctly, then they should:

  • Change the patch number when fixing a bug as long as it doesn’t break any APIs or adds features.
  • Change the minor number when they added features that don’t break any APIs.
  • Change the major number when they do break APIs.

This is why “Up to Next Major” works so well, because it should mean you get new bug fixes and features over time, but won’t accidentally switch to a version that breaks your code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment