rust-release

To safely publish a Rust crate from a multi-crate workspace, use a verification-first workflow that reads Cargo.toml and CI workflows to validate version bumps, tags, and publish readiness before mutating history.

A verification-first Rust release workflow automates crate publishing by validating tags and publish readiness using Cargo.toml and AGENTS.md, ensuring only audited releases proceed to a registry.

Yes, you can automate version bumping and tagging for Rust crates while enforcing checks, applying guarded release checks that read workspace layouts and inspect commits before creating tags.

Yes, this Rust release process reads AGENTS.md, Cargo.toml, and existing CI workflows to determine publish scope and validate readiness using a repo-native wrapper for commands.

The best way to prevent invalid tags during Rust crate publishing is to follow a guarded release workflow that audits repository state and validates tags before proceeding with the publish step.

Your Rust crate release might fail readiness checks because the verification workflow reads workspace layouts and Cargo.toml to gate publishing, stopping releases that lack validated version bumps or tags.