Version Bump

Semantic Versioning Skill

This skill helps determine appropriate version bumps following Semantic Versioning.

Version Format

MAJOR.MINOR.PATCH

• MAJOR: Breaking changes
• MINOR: New features, backwards compatible
• PATCH: Bug fixes, backwards compatible

Version Bump Decision Tree

MAJOR (X.0.0) - Breaking Changes

Bump MAJOR when you make incompatible API changes:

• Removed public functions, methods, or types
• Changed function signatures (parameters, return types)
• Renamed public APIs
• Changed default behavior that breaks existing usage
• Removed CLI flags or changed their meaning
• Changed configuration file format incompatibly

MINOR (0.X.0) - New Features

Bump MINOR when you add functionality in a backwards compatible manner:

• New commands or subcommands
• New CLI flags
• New configuration options
• New output formats
• New integrations or providers

PATCH (0.0.X) - Bug Fixes

Bump PATCH when you make backwards compatible bug fixes:

• Fix incorrect behavior
• Fix crashes or errors
• Performance improvements (no API changes)
• Documentation fixes
• Internal refactoring (no behavior changes)

Quick Reference

Pre-1.0 Versioning

For versions < 1.0.0 (like this project):

• MINOR can include breaking changes
• PATCH is for bug fixes and small features
• More flexibility before reaching stability

Instructions

1. Review all changes since last release:

   git log --oneline $(git describe --tags --abbrev=0)..HEAD
   

2. Check for breaking changes:

   • Removed or renamed public APIs?
   • Changed default behaviors?
   • Incompatible configuration changes?

3. If breaking changes exist -> MAJOR bump

4. If new features exist -> MINOR bump

5. If only fixes/refactoring -> PATCH bump

Version Update Locations

When bumping version, update:

1. Cargo.toml - version = "X.Y.Z"
2. CHANGELOG.md - Add ## [X.Y.Z] - YYYY-MM-DD section
3. Version links - Update comparison URLs at bottom of CHANGELOG.md

Converted and distributed by TomeVault — claim your Tome and manage your conversions.