release

You can automate Rust crate publishing by using this skill to manage SemVer version bumping, verify build and linting status, and execute release commands including tagging and pushing to your repository via CI for crates.io.

Handling SemVer version bumps for Rust releases requires guiding through patch, minor, or major version increments. This skill automates that process, correctly updating your crate version and ensuring tests pass before committing changes.

Yes, you can verify tests and linting pass before publishing a new crate version. This skill performs state verification to ensure all checks succeed before executing release commands and pushing the new version to your repository.

Yes, the release automation process handles git tagging and pushing. It executes release commands, commits the version bump, creates the necessary tags, and pushes changes directly to your repository as part of the publishing workflow.

You need an automated release workflow for Rust crates when you have completed a new feature and want to ensure versioning consistency. It is used to correctly bump the SemVer version, run checks, and publish to crates.io without manual errors.