po4yka/rust-skills / skills/rust-crate-release
rust-crate-release
VerifiedUse when preparing to publish a Rust crate or a Rust binary release, or recovering from a bad one - deciding a SemVer bump or MSRV change, checking cargo package and cargo publish output, ordering a workspace publish, setting up crates.io trusted publishing, deciding whether to yank a crate version, building a release archive with a release checksum, release SBOM, and attestation, or using cosign to sign release artifacts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| references/binary-distribution.md | markdown | 15.3 KB |
| references/compatibility.md | markdown | 6.6 KB |
| references/package-inspection.md | markdown | 2.4 KB |
| references/recovery.md | markdown | 2.5 KB |
| references/release-inputs-and-metadata.md | markdown | 2.5 KB |
| references/trusted-publishing.md | markdown | 6.3 KB |
| references/workspace-publish.md | markdown | 1.5 KB |
references/workspace-publish.md
View on GitHub# Workspace Publish Order
Read this when one release publishes more than one package from a workspace. Each upload is an
external write; the safety rules in `SKILL.md` apply to every package in the set.
## Choose and order the packages
Publish only the packages that changed, plus the dependents that need their new versions.
Publish dependencies before dependents. For a dependency with `path` and `version`, confirm that
`version` selects the release the dependent needs.
## Dry-run the whole set
Verify the whole ordered set in one dry run before the first upload:
```bash
cargo publish --locked --dry-run --registry <registry> -p <dependency> -p <dependent>
```
Since Cargo 1.90, this resolves each new workspace version from a local overlay. A dry run of the
dependent alone fails until the dependency is in the index: `no matching package named` for a new
crate, and `failed to select a version for the requirement` for a new version of a published
crate.
Run the package listing and archive checks (`SKILL.md` section 7) for each package.
## Publish
Multi-package `cargo publish` is not atomic: a server error leaves earlier packages published.
Publish one package at a time when you need a stop point after each upload. Request authorization
with the complete ordered list. Stop after the first failed or uncertain publish.
## Official references
- [`cargo publish`](https://doc.rust-lang.org/cargo/commands/cargo-publish.html)
- [Cargo changelog](https://doc.rust-lang.org/nightly/cargo/CHANGELOG.html)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |