version-release

Automating versioning based on Git commit history involves analyzing commit messages to determine version bumps, updating Cargo files, generating release notes, and creating Git tags automatically. This reduces manual effort and ensures consistency.

Yes, you can manually override the version number during release automation. The process includes a user confirmation step for the determined version, allowing you to apply manual overrides before updating Cargo.toml and creating Git tags.

Yes, this release automation tool supports Cargo-based projects. It specifically handles updates to Cargo.toml and Cargo.lock files, making it suitable for developers working within the Rust ecosystem who use Conventional Commits.

The best way to generate release notes and annotated Git tags automatically is to use a release automation workflow that parses commit history to determine the version bump, updates dependencies, and creates tags upon user confirmation.

Following Conventional Commits is highly recommended for automated version determination. The system relies on your commit history to calculate the correct version bump, ensuring accurate updates to Cargo files and release notes.

Automated version release requires user confirmation to prevent incorrect version bumps. It allows you to review the determined version number extracted from commit history and manually override it before applying changes to Cargo.lock and Git tags.