release-bump

Automating Rust workspace version bumps involves updating version fields across internal crate Cargo.toml files for consistency. This Skill modifies the files, builds, tests, commits, pushes, and tags the release to streamline the workflow.

Triggering a release workflow after committing fixes to ralph-orchestrator is handled by bumping the workspace version and running the publish sequence. This Skill applies the version bump, rebuilds, tests, and pushes a new vX.Y.Z tag to the remote repository.

Git and Cargo are required to bump versions and tag a release because the Skill modifies Cargo.toml files and executes Git operations. A configured remote repository is also necessary to commit, push, and tag the release.

Workspace version bumping ensures internal crate consistency by applying the new version number across all Cargo.toml files in the workspace. This guarantees every internal crate shares the same version before the build and tag sequence begins.

A release pipeline might fail after manually updating the workspace Cargo.toml version if internal crate versions remain inconsistent or tests fail. This Skill automates the bump, build, and test sequence to prevent these manual update errors before tagging.

This release bump process is specifically designed for the ralph-orchestrator project to automate its workspace versioning and tagging. It targets the ralph-orchestrator version fields and orchestrates the specific build, test, and publish workflow required for that release.