cargo-release

Automating Rust workspace releases involves analyzing code changes, suggesting version bumps based on dependency impact, updating Cargo.toml files, and creating a single atomic commit with multiple tags. This process optionally publishes to crates.io while managing internal dependency order.

The best way to handle version bumping in a Rust cargo workspace is using heuristics that analyze code changes and dependency impact. This approach intelligently suggests appropriate version increments and automatically updates internal dependencies across the workspace.

Yes, you need cargo-edit installed to use this release workflow. It serves as a required dependency for managing and updating Cargo.toml files during the automated version bumping and tagging process.

Yes, you can automatically publish multiple interdependent crates to crates.io. The workflow handles topological sorting for release order, validates against the registry, and executes publishing with robust error handling for a safe release.

Multi-crate Rust publishing requires topological sorting to manage internal dependency updates and determine the correct release order. This ensures that prerequisite crates are published before their dependents, preventing failed registry submissions.