🏷️

Semantic Versioning

Verified

by Community

Understand and apply semantic versioning. Determine when to bump major, minor, or patch versions with practical examples.

semverversioningreleasedevelopment

Semantic Versioning Skill

Apply SemVer correctly.

Format: MAJOR.MINOR.PATCH

  • MAJOR (X.0.0) — Breaking changes
  • MINOR (0.X.0) — New features, backward compatible
  • PATCH (0.0.X) — Bug fixes, backward compatible

When to Bump

| Change | Bump |

|--------|------|

| Remove a public API method | MAJOR |

| Change a function signature | MAJOR |

| Add a new endpoint | MINOR |

| Add optional parameter | MINOR |

| Fix a bug | PATCH |

| Improve performance | PATCH |

| Update dependencies | PATCH |

| Security fix | PATCH |

Pre-release

1.0.0-alpha.1
1.0.0-beta.1
1.0.0-rc.1

Current Version

cat package.json | python3 -c "import json,sys; print(json.load(sys.stdin).get('version','N/A'))"

Guidelines

  • Start at 0.1.0 for initial development
  • 1.0.0 signals stable public API
  • Document breaking changes in CHANGELOG