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/release-inputs-and-metadata.md
View on GitHub# Release inputs and manifest metadata
Contents:
- Release inputs
- Read-only checks
- `[package]` metadata
- docs.rs metadata
- Official references
## Release inputs
Collect these values first:
| Input | Required evidence |
|---|---|
| Package | Exact Cargo package name and manifest path |
| Registry | `crates-io` or one configured registry name |
| Base | Previous published version and its source tag, or `none` for a first release |
| Candidate | Exact commit to release |
| Version | Proposed new version |
| MSRV | Effective `package.rust-version` and the project support policy |
| Features | Default set and every supported non-default combination |
| Targets | Supported target and operating-system policy |
| Mode | Registry package, binary distribution, or both |
| Channel | Local `cargo publish`, or a CI workflow that a tag or dispatch starts |
| Authority | Who can approve publish, tags, releases, uploads, signing, yanks, and owner changes |
## Read-only checks
Run these checks before any other step. They write nothing:
```bash
git status --short
git rev-parse HEAD
git tag --list --sort=-version:refname
cargo metadata --locked --no-deps --format-version 1
```
## `[package]` metadata
Verify these `[package]` values for the package that ships:
```toml
[package]
name = "<package>"
version = "<version>"
rust-version = "<msrv>"
description = "<one-line description>"
license = "<SPDX expression>"
repository = "<source URL>"
readme = "README.md"
```
Use `license-file` instead of `license` only for a nonstandard license, and confirm the file
enters the archive. Check every README link as it renders on the registry page. Do not set
`homepage` to the `repository` or documentation URL.
## docs.rs metadata
docs.rs announced that from 2026-05-01 it builds only the default target (`default-target`, else
`x86_64-unknown-linux-gnu`) unless `targets` lists more. Set `targets` explicitly when the public
API differs by target, or users see no documentation for the other targets:
```toml
[package.metadata.docs.rs]
features = ["<documented-feature>"]
targets = ["x86_64-unknown-linux-gnu", "<other-supported-target>"]
```
Use `all-features = true` only when the features are additive.
## Official references
- [Cargo publishing](https://doc.rust-lang.org/cargo/reference/publishing.html)
- [`cargo info`](https://doc.rust-lang.org/cargo/commands/cargo-info.html)
- [docs.rs build metadata](https://docs.rs/about/metadata)
- [docs.rs default target change](https://blog.rust-lang.org/2026/04/04/docsrs-only-default-targets/)
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 |