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/recovery.md
View on GitHub# Release Recovery and Owners
Read this when you consider a yank, a crate deletion, an owner change, or a RustSec advisory for
your own release. Every command here is an external write: get authorization for the exact
command first.
## Recover from a bad release
Do not use a yank as the normal fix. Publish a compatible fixed version first, when possible.
Check exact-version dependents and supported release lines before any yank.
Yank only for an exceptional defect: an accidental publish, an unintended SemVer break, or a
seriously broken version. Get authorization first.
```bash
cargo yank <package>@<version> --registry <registry>
cargo yank <package>@<version> --undo --registry <registry>
```
A yank blocks new resolutions; `cargo update --precise <version>` can still select it. It does
not break existing lockfiles, delete downloads, or remove a leaked secret.
crates.io lets an owner delete a whole crate only when it was published less than 72 hours ago,
or when it has one owner, fewer than 1000 downloads for each month, and no reverse dependencies
on crates.io. Deletion is an external write that needs authorization. It does not recall
downloaded copies.
If a secret entered the archive, revoke the secret first, then contact the registry. Do not wait
for a yank or a deletion.
For a vulnerability in your own release, publish the fixed release first. Then file a RustSec
advisory: a crate owner opens a pull request against `rustsec/advisory-db` with a file in
`crates/<package>/` ([RustSec contributing](https://rustsec.org/contributing.html)). Request a
CVE or a GitHub Security Advisory when the project wants one, and add its ID to `aliases`. Each
step is an external write that needs authorization.
## Manage owners separately
```bash
cargo owner --list <package> --registry <registry>
```
A named owner can publish, yank, and change owners. A crates.io team owner can publish and yank,
but cannot change owners. Prefer a team owner when the registry supports it.
Get authorization for one exact command, run only that command, then list the owners again and
report the final set:
```bash
cargo owner --add <account-or-team> <package> --registry <registry>
cargo owner --remove <account-or-team> <package> --registry <registry>
```
## Official references
- [crates.io policies](https://crates.io/policies)
- [`cargo yank`](https://doc.rust-lang.org/cargo/commands/cargo-yank.html)
- [`cargo owner`](https://doc.rust-lang.org/cargo/commands/cargo-owner.html)
- [RustSec contributing](https://rustsec.org/contributing.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 |