cargo-release

Automated Rust crate publishing uses a phase-driven workflow to bump versions in Cargo.toml, update Cargo.lock, commit changes, tag the release, and publish to crates.io. This ensures consistency across local and CI release pipelines for Rust projects.

The best way to release a Rust library or binary end-to-end is an automated workflow that handles version bumping, git operations, and crate publishing. This applies across local and CI release pipelines, including GitHub releases and crate publishing.

Yes, you can trigger GitHub release workflows automatically when publishing a Rust crate. The workflow integrates GitHub Release creation and triggers release workflows automatically, ensuring reliable releases with validation steps and checks in CI pipelines.

Yes, automated Rust release workflows support validation steps, cargo checks, and automatic retries in CI pipelines. The workflow satisfies requirements such as argument validation, cargo checks, git push, and gh workflow triggering to ensure a reliable release.

Update Cargo.toml and Cargo.lock versions by running the automated release command with a target version, such as specifying 0.2.0. The workflow bumps the version in Cargo.toml and updates Cargo.lock as part of its phase-driven release process.