cargo-release
This skill automates the complete Cargo release workflow for Rust monorepos, enforcing a 10-step sequence that includes semver versioning, dependency updates, test and lint gates, git tagging, and crates.io publishing. It handles cross-crate dependency ordering, workspace version management for the trusty-mpm family, and includes critical macOS codesign safety rules to prevent signing cache crashes.
cargo-release executes a 10-step Cargo publish sequence with semver rules and quality gates for Rust monorepos.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-18
cargo-release executes a 10-step Cargo publish sequence with semver rules and quality gates for Rust monorepos. This skill automates the complete Cargo release workflow for Rust monorepos, enforcing a 10-step sequence that includes semver versioning, dependency updates, test and lint gates, git tagging, and crates.io publishing. It handles cross-crate dependency ordering, workspace version management for the trusty-mpm family, and includes critical macOS codesign safety rules to prevent signing cache crashes.
Use it when
- cargo-release enforces semantic versioning by automatically determining whether to bump major, minor.
- cargo-release manages cross-crate dependencies by calculating the correct publication order and updating internal monorepo references.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
bobmatnyc/claude-mpm-skills/cargo-release · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to release a Rust crate using cargo-release?
cargo-release automates the complete Cargo release workflow through a 10-step sequence. The skill enforces semver versioning rules, updates cross-crate dependencies, runs quality gates (test and clippy), creates git tags, and publishes to crates.io in the correct dependency order. This ensures monorepo releases maintain consistency and prevent publishing errors from incorrect sequencing.
What semver bump rules does cargo-release apply?
cargo-release enforces semantic versioning by automatically determining whether to bump major, minor, or patch versions based on the changes detected. The skill integrates semver rules into its 10-step release sequence, ensuring version increments follow Rust ecosystem conventions and preventing manual versioning mistakes across monorepo crates.
How does cargo-release handle cross-crate dependencies?
cargo-release manages cross-crate dependencies by calculating the correct publication order and updating internal monorepo references before publishing to crates.io. When bumping versions in a workspace, the skill updates all dependent crates' Cargo.toml files and respects dependency graphs to ensure no crate publishes before its dependencies are ready.
What macOS codesign safety rules prevent binary install crashes?
cargo-release includes critical macOS codesign safety rules that prevent signing cache crashes when installing release binaries. The skill recommends proper binary installation procedures and codesign handling to avoid the common macOS issue where cached signatures cause installation failures, ensuring reliable binary deployment on macOS systems.
Does cargo-release support the trusty-mpm family with shared versioning?
Yes, cargo-release supports the trusty-mpm family with shared workspace versioning. The skill manages version bumps across the trusty-tools ecosystem, coordinating releases where multiple related crates share version numbers and maintaining consistency across the family during the complete release sequence.
What quality gates does cargo-release enforce before publishing?
cargo-release enforces quality gates including cargo test and clippy lint checks as part of its 10-step release protocol. These gates run before git tagging and crates.io publication, ensuring only code that passes all checks reaches the registry and preventing defective releases from being published.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Cargo Release Protocol
When to Invoke
Invoke this protocol when the user says: "release", "publish", "bump version", "ship", "tag a release", or "cut a version" for any
(truncated - see the full file via the links below)
File tree — 2 files
toolchains/rust/ops/cargo-release/SKILL.md
toolchains/rust/ops/cargo-release/metadata.json
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Execute a 10-step Cargo release with semver rules and quality gates”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This protocol enforces a three-stage quality check for Rust code: format validation, clippy linting, and test execution, each halting on failure. It's designed for the trusty-tools monorepo and clarifies crate naming conventions, test output interpretation, and handling of pre-existing failures. Use it before any PR merge or when code changes are ready to commit.
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.
This guide explores Swift's native concurrency model, contrasting it with legacy Grand Central Dispatch approaches. You'll examine the cooperative thread pool, async/await state machines, structured concurrency hierarchies, and the Actor model's data safety guarantees. The material covers Swift 6 strict concurrency requirements, migration tactics, and synchronization primitives for building robust applications.
RFC Writer guides you through composing normative RFCs—product contracts with observable obligations, invariants, and compatibility rules. It enforces separation between specification prose and implementation details, ensures each clause is independently testable, and hands off lifecycle operations to dedicated governance tools. Use it to author the contract itself, not design rationale or execution scope.
Swift 6 marks a fundamental evolution from application-focused language to systems programming platform, introducing strict ownership semantics and compile-time concurrency verification. This skill dissects the language's architectural transformation through noncopyable types, region-based isolation, and embedded systems capabilities that eliminate entire classes of memory safety vulnerabilities. Designed for senior architects and lead engineers, it equips you with the theoretical foundations and practical patterns needed to leverage Swift 6's safety guarantees across microcontrollers, servers, and distributed systems.
Ship orchestrates the full release cycle for RTK projects: quality verification, semantic versioning, changelog generation, git tagging, and remote push to activate CI/CD pipelines. Follow pre-release checklists, execute the multi-step workflow, and verify post-release artifacts automatically.