release-bump

To automate a Cargo workspace version bump, update the workspace version in Cargo.toml and propagate it to internal crates using version.workspace = true. This ensures all crates in the workspace share the new version number consistently.

Coordinating a git release involves running cargo build and cargo test, then committing the version bump, pushing to the main branch, and creating a git tag to initiate the release pipeline.

Yes, the release workflow requires running cargo build and cargo test to verify publish readiness before performing git operations to commit, push, and tag the release.

Version workspace propagation works by setting the version in the root Cargo.toml, which automatically applies that version to all inheriting crates, ensuring consistency before you commit and tag the release.

Yes, after bumping the workspace version and confirming the change, the workflow commits the update, pushes to the main branch, applies a git tag, and prepares a GitHub release to start the pipeline.

You should not use an automated version bump if your crates require independent versioning, as this workflow assumes all internal crates inherit a single workspace version from the root Cargo.toml.