القائمة
Synchronously bump all crate versions + Roon Extension display_version + path dep versions in the roon-rs workspace. Runs build/test/clippy to verify, then stages changes for commit.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | bump-version |
| description | Synchronously bump all crate versions + Roon Extension display_version + path dep versions in the roon-rs workspace. Runs build/test/clippy to verify, then stages changes for commit. |
| user-invocable | true |
| allowed-tools | ["Read","Edit","Bash","Grep"] |
| argument-hint | <new-version> |
Bump the roon-rs workspace to a new unified version. Updates all three categories of version strings atomically:
Cargo.tomlCargo.toml (e.g., roon-api = { path = "...", version = "X.Y.Z" })display_version string passed to RoonClientBuilder::new in application source codeAfter editing, runs cargo build/test/clippy and stages all changes. Does NOT commit or tag — user reviews the diff and decides.
$ARGUMENTS is the target version (semver, e.g., 0.2.0, 1.0.0-rc.1). Required.
If no argument, print usage and exit:
Usage: /bump-version <new-version>
Example: /bump-version 0.2.0
Before touching any files, run git status --short. The working tree should be clean (or contain only changes the user explicitly intends to bundle into the bump commit). If unrelated unstaged or untracked files are present, surface them via AskUserQuestion and let the user decide whether to:
git stash push -u -m "pre-bump"Reason: Step 5 rewrites Cargo.lock in place. If unrelated edits already touch tracked files, the resulting git add is hard to review and easy to mis-stage. Catching this upfront is cheaper than untangling it post-build.
Read crates/roon-api/Cargo.toml and extract the version = "..." line from [package]. This is the reference "current version". If any other crate has a different version (e.g., roon-mcp was already bumped independently), warn the user and ask whether to:
Use AskUserQuestion for this.
Update version = "..." in [package] section of these 6 Cargo.toml files:
| File | Current Line |
|---|---|
crates/roon-moo/Cargo.toml | version = "<current>" |
crates/roon-sood/Cargo.toml | version = "<current>" |
crates/roon-api/Cargo.toml | version = "<current>" |
crates/roon-cli/Cargo.toml | version = "<current>" |
crates/roon-hub/Cargo.toml | version = "<current>" |
crates/roon-mcp/Cargo.toml | version = "<current>" |
Use Edit tool with exact string match. The version = "X.Y.Z" line appears in [package] section near the top and is unique per file (only one version = "..." at file level).
Update internal workspace dependencies (format: name = { path = "...", version = "X.Y.Z" }). Use replace_all = true on each file since multiple internal deps may share the same version:
| File | Internal deps to update |
|---|---|
crates/roon-api/Cargo.toml | roon-moo, roon-sood (deps + dev-deps) |
crates/roon-cli/Cargo.toml | roon-api, roon-sood |
crates/roon-hub/Cargo.toml | roon-api |
crates/roon-mcp/Cargo.toml | roon-api |
For each file, run:
grep -n 'version = "<current>"' <file>
to confirm which lines are path deps (not the [package] version which was handled in Step 2). Then edit those specific lines.
The display_version is the 3rd positional argument to RoonClientBuilder::new(...). Update these application source files:
| File | Line context |
|---|---|
crates/roon-cli/src/connect.rs | Inside RoonClientBuilder::new(...) — the "X.Y.Z" string literal on its own line |
crates/roon-mcp/src/main.rs | Inside RoonClientBuilder::new(...) — the "X.Y.Z" string literal on its own line |
Do NOT touch:
crates/roon-api/examples/*.rs — reference examples, identity stays stablecrates/roon-api/tests/*.rs — test fixtures use "1.0" / "1.0.0" as arbitrary identifierscrates/roon-hub/src/main.rs — reads display_version from TOML config, no hardcoded stringLocate the line with Grep (pattern: "<current>" inside the 5-line block after RoonClientBuilder::new) and use Edit with enough context to match uniquely.
Run in sequence (stop on first failure):
cargo fmt --all
cargo build --workspace
cargo test --workspace
cargo clippy --workspace --tests -- -D warnings
If anything fails, DO NOT stage changes. Report the failure to the user for inspection. If clippy has autofixable warnings, run cargo clippy --workspace --tests --fix --allow-dirty and re-run fmt, then re-verify.
If all verifications pass:
git add Cargo.lock crates/*/Cargo.toml crates/roon-cli/src/connect.rs crates/roon-mcp/src/main.rs
git diff --cached --stat
git diff --cached
Cargo.lock is regenerated by cargo build in Step 5 with the new versions and MUST be staged together — committing Cargo.toml without the matching lockfile leaves the workspace in a broken state for downstream consumers (and for cargo publish dry-runs).
Report to the user:
git diff --cached --stat outputrelease: bump version to <new-version>
Sync all crate versions, path dep constraints, and Roon Extension
display_version to <new-version> in preparation for v<new-version> release.
git tag v<new-version> && git push origin v<new-version> to trigger cargo-dist release + crates.io publish workflows.git tag. Once the tag is pushed, git commit --amend becomes destructive — the published tag keeps pointing at the pre-amend commit, which then becomes orphaned from main. cargo-dist will have already built artifacts and cargo publish will have already pushed the (possibly broken) version to crates.io — and crates.io is immutable, so recovery requires a fresh patch version (e.g. 0.4.0 → 0.4.1) instead.Do NOT commit or tag automatically — user reviews first.
Edit fails because the expected string isn't found, the file may have been manually edited. Stop, show the user the actual file contents around the expected location, and ask how to proceed.git checkout . to discard.