version-bump

Bump Cargo.toml versions across Rust workspace crates and commit.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/dataroadinc/rhusky --skill version-bump-dataroadinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/dataroadinc/rhusky/tree/main/.claude/skills/version-bump
Command: npx skills add https://github.com/dataroadinc/rhusky --skill version-bump-dataroadinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bump the version in Cargo.toml to ensure releases are properly versioned and reproducible across the workspace.

Core Features & Use Cases

  • Automated version bumps: Update the Cargo.toml version field consistently for a new release.
  • Release hygiene: Prepare a commit message like chore(version): bump X.Y.Z -> A.B.C and update related files as needed.
  • Traceability: Keeps version changes auditable via VCS history.

Quick Start

Edit Cargo.toml to the new version and commit with a conventional message.

Frequently Asked Questions about version-bump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bump the version in Cargo.toml for a Rust workspace release?

To bump the version in Cargo.toml, edit the version field and run cargo update --workspace to synchronize crates. This ensures releases are properly versioned and reproducible across the workspace.

What is the best way to automate Cargo.toml version bumps across a Rust workspace?

Automating Cargo.toml version bumps updates the version field consistently across all workspace crates. It stages changes and commits with a conventional message like chore(version): bump X.Y.Z -> A.B.C for VCS traceability.

Does cargo update --workspace synchronize version bumps for all Rust crates?

Yes, cargo update --workspace synchronizes version bumps across all Rust crates in the workspace. Running this after editing Cargo.toml ensures dependencies reflect the new release version consistently.

How do I commit a version bump in Rust with a conventional message?

To commit a version bump in Rust with a conventional message, stage the updated Cargo.toml files and commit using the format chore(version): bump X.Y.Z -> A.B.C. This keeps version changes auditable via VCS history.

When should I use a workspace version bump instead of updating single Cargo.toml files?

Use a workspace version bump when a Rust project requires synchronized version updates across multiple crates. This ensures release hygiene and reproducibility by updating all related Cargo.toml files together in one commit.