{"enrichment":{"faq":[{"a":"release-bump automates version bumping across all ralph-orchestrator crates in your workspace. It updates the workspace Cargo.toml file to set your new version, then coordinates with your CI/CD pipeline to run tests, create git tags, and trigger automated builds. The skill handles all version locations simultaneously, ensuring consistency across crates.","q":"How do I bump the version for ralph-orchestrator?"},{"a":"release-bump manages the complete release workflow for ralph-orchestrator. It bumps versions across all crates, updates workspace Cargo.toml, runs test validation, creates git tags, and pushes changes to trigger CI/CD. This automation coordinates with GitHub Actions to build binaries and publish to both crates.io and npm in a single coordinated workflow.","q":"What does release-bump do in the ralph-orchestrator release process?"},{"a":"release-bump manages version synchronization across your entire ralph-orchestrator workspace by updating all seven version locations at once through the workspace Cargo.toml. This ensures all crates stay in sync during release, eliminating manual version management across multiple files and preventing version mismatches between interdependent crates.","q":"How does release-bump handle multi-crate version synchronization?"},{"a":"Yes, release-bump fully automates the release workflow by integrating with your CI/CD pipeline. After you confirm the version bump, it creates git tags and pushes changes to trigger GitHub Actions. The pipeline then builds binaries, runs tests, and publishes your release to crates.io and npm automatically without manual intervention.","q":"Can release-bump automate the entire release workflow with CI/CD?"},{"a":"release-bump updates your workspace Cargo.toml with the new version and propagates it across all ralph-orchestrator crates. It then validates the changes by running tests, creates a git tag for the release, and pushes to your repository to trigger automated CI/CD jobs that build and publish to crates.io and npm.","q":"What happens when I update workspace Cargo.toml version with release-bump?"}],"shadow_tags":["version-management","release-automation","cargo-workflow","rust-publishing","ci-cd-integration","semantic-versioning","git-tagging","multi-crate-sync"],"summary_rewrite":"Automate version bumping and release workflows for ralph-orchestrator by updating the workspace Cargo.toml file and pushing tags to trigger CI. The skill handles all seven version locations, runs tests, and coordinates with GitHub Actions to build binaries and publish to crates.io and npm."},"files":[{"bytes":2334,"path":".claude/skills/release-bump/SKILL.md","sha256":"97c3aae11e7f2f34a682ce2af33f3016888a99ceec136948b957a527edf2b06b","url":"https://skillfed.io/files/mikeyobrien/ralph-orchestrator/release-bump/d39491f8/SKILL.md"}],"id":"mikeyobrien/ralph-orchestrator/release-bump","links":{"html":"https://skillfed.io/mikeyobrien/ralph-orchestrator/release-bump","md":"https://skillfed.io/mikeyobrien/ralph-orchestrator/release-bump.md","repo":"https://github.com/mikeyobrien/ralph-orchestrator"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":290,"language":"Rust","last_updated":"2026-07-25","license":"MIT","name":"release-bump","publisher":"mikeyobrien","stars":3077},"relations":{"similar":[{"id":"CuriousLearner/devkit/rust-cargo-assistant"},{"id":"terrylica/cc-skills/run-full-release"},{"id":"rtk-ai/rtk/ship"},{"id":"existential-birds/beagle/rust-project-setup"},{"id":"mohitmishra786/low-level-dev-skills/cargo-workflows"},{"id":"wasabeef/claude-code-cookbook/update-rust-deps"},{"id":"mikeyobrien/ralph-orchestrator/tmux-terminal"},{"id":"max-sixty/worktrunk/release"},{"id":"bobmatnyc/claude-mpm-skills/cargo-release"},{"id":"dchuk/claude-code-tauri-skills/tauri-updating-dependencies"}]},"slug":{"owner":"mikeyobrien","repo":"ralph-orchestrator","skill":"release-bump"},"version":"d39491f8"}