release-bump
Handles version bumping and release publishing for Ralph Orchestrator.
Install
mkdir -p .claude/skills/release-bump && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5933" && unzip -o skill.zip -d .claude/skills/release-bump && rm skill.zipInstalls to .claude/skills/release-bump
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publishKey capabilities
- →Sync version strings across multiple Cargo.toml files
- →Verify workspace inheritance in dependency trees
- →Execute build and test commands prior to committing
- →Generate release tags automatically
How it works
Uses search-and-replace scripts to update version definitions in both workspace and individual crate configurations before triggering CI validation.
Inputs & outputs
When to use release-bump
- →Bump project version
- →Publish a new release
- →Update internal dependency versions
About this skill
Release Bump
Overview
Bump version and trigger release for ralph-orchestrator. All versions live in workspace Cargo.toml - individual crates inherit via version.workspace = true.
Confirm the new version with the user. Once the bump commit is pushed, track progress of the release.
Quick Reference
| Step | Command/Action |
|---|---|
| 1. Bump version | Edit Cargo.toml: replace all version = "X.Y.Z" (7 occurrences) |
| 2. Build | cargo build (updates Cargo.lock) |
| 3. Test | cargo test |
| 4. Commit | git add Cargo.toml Cargo.lock && git commit -m "chore: bump to vX.Y.Z" |
| 5. Push | git push origin main |
| 6. Tag | git tag vX.Y.Z && git push origin vX.Y.Z |
Version Locations (All in Cargo.toml)
# Line ~17 - workspace version
[workspace.package]
version = "X.Y.Z"
# Lines ~113-118 - internal crate dependencies
ralph-proto = { version = "X.Y.Z", path = "crates/ralph-proto" }
ralph-core = { version = "X.Y.Z", path = "crates/ralph-core" }
ralph-adapters = { version = "X.Y.Z", path = "crates/ralph-adapters" }
ralph-tui = { version = "X.Y.Z", path = "crates/ralph-tui" }
ralph-cli = { version = "X.Y.Z", path = "crates/ralph-cli" }
ralph-bench = { version = "X.Y.Z", path = "crates/ralph-bench" }
Tip: Use Edit tool with replace_all: true on version = "OLD" → version = "NEW" to update all 7 at once.
What CI Does Automatically
Once you push the tag, .github/workflows/release.yml triggers and:
- Creates the GitHub Release with auto-generated notes
- Builds binaries for macOS (arm64, x64) and Linux (arm64, x64)
- Uploads artifacts to the GitHub Release
- Publishes to crates.io (in dependency order)
- Publishes to npm as
@ralph-orchestrator/ralph
Common Mistakes
| Mistake | Fix |
|---|---|
| Only updating workspace.package.version | Must update all 7 occurrences including internal deps |
| Forgetting to run tests | Always cargo test before commit |
Creating release manually with gh release create | Just push the tag - CI creates the release with artifacts |
| Pushing tag before main | Push main first, then push the tag |
When not to use it
- →During early development phases where semantic versioning is irrelevant
- →If the repository uses a non-workspace crate structure
Prerequisites
Limitations
- →Limited to the specific ralph-orchestrator structure
- →Manual confirmation required to ensure all 7 file locations are addressed
How it compares
It enforces global project-wide consistency in versioning, specifically mitigating issues where internal workspace dependencies drift.
Compared to similar skills
release-bump side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release-bump (this skill) | 1 | 5mo | No flags | Beginner |
| release-skills | 2 | 3mo | Review | Intermediate |
| hula-skill | 3 | 7mo | Review | Intermediate |
| analyze-ci-speed | 1 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mikeyobrien
View all by mikeyobrien →You might also like
release-skills
JimLiu
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送".
hula-skill
HuLaSpark
HuLa project skill for frontend (Vue 3 + Vite + UnoCSS + Naive UI/Vant), backend (Tauri v2 + Rust + SeaORM/SQLite), full-stack flows, and build/release work. Use when the user mentions hula or HuLa or requests changes in this repository; after triggering, ask which scope (frontend/backend/fullstack/build-release) to enable.
analyze-ci-speed
Sovereign-Labs
Analyze compilation time and test durations from CI logs. Use when the user asks about slow builds, slow tests, or wants to optimize CI time.
cts-triage
gfx-rs
Run CTS test suites and investigate failures
pre_commit
pums974
Standardized pre-commit workflow for linting, formatting, and local quality gates.
rust-build
keychat-io
Build Rust native libraries for the FFI plugin