cargo-yank

Yank version from registry

$ cargo yank [crate@1.0.0]

$ cargo yank --version [1.0.0] [crate]

$ cargo yank --undo [crate@1.0.0]

$ cargo yank --registry [my-registry] [crate@1.0.0]

cargo yank [options] crate@version
cargo yank [options] --version version [crate]

cargo yank marks a crate version as yanked on the registry. Yanked versions cannot be used as new dependencies but existing Cargo.lock files continue to work. Does not delete data.
Requires authentication via cargo login.

--version version

Version to yank

Restore yanked version

Target registry

Registry index URL

API token

Verbose output

Suppress output

Yanked versions
- Cannot be added as new dependencies
- Existing Cargo.lock references still work
- Not deleted from registry

- Accidental publish
- Unintentional semver breakage
- Significantly broken functionality
- Security issues (consider RustSec instead)

Publish a fixed version (e.g., 1.5.1) before yanking the broken version (1.5.0).

crates.io is a permanent archive; yanking marks version unavailable but doesn't delete. For security issues, RustSec advisories are less disruptive.

cargo(1), cargo-publish(1), cargo-owner(1)