bump-version

You can automate version bumps by updating the version field in Cargo.toml and generating categorized entries in CHANGELOG.md from your commit history. This ensures semantic versioning compliance and reduces manual errors during software releases.

Automatic changelog generation works by parsing your git commit history and organizing changes into categorized sections within CHANGELOG.md, such as Features and Fixes. This provides a clear, maintained release history without manual sorting.

Yes, you can use this to update the version field in Cargo.toml to a specified semantic version. It manages the version update process to ensure your project versioning artifacts are correctly aligned for release.

The best way to prepare a release is to automate both the version bump in Cargo.toml and the changelog update. This approach ensures semantic versioning compliance and maintains an accurate release history while saving development time.

No, this versioning automation does not require any specific dependencies or components to function. It operates independently to parse git commit history and update project versioning files.