cargo-yank - Remove a pushed crate from the index
cargo yank [options] --vers version [crate]
The yank command removes a previously published crate's version from the
server's index. This command does not delete any data, and the crate will
still be available for download via the registry's download link.
Note that existing crates locked to a yanked version will still be
able to download the yanked version to use it. Cargo will, however, not
allow any new crates to be locked to any yanked version.
This command requires you to be authenticated with either the
--token option or using cargo-login(1).
If the crate name is not specified, it will use the package name
from the current directory.
The version to yank or un-yank.
Undo a yank, putting a version back into the index.
API token to use when authenticating. This overrides the
token stored in the credentials file (which is created by
variables can be used to override the tokens stored in the credentials file.
The token for crates.io may be specified with the
CARGO_REGISTRY_TOKEN environment variable. Tokens for other
registries may be specified with environment variables of the form
CARGO_REGISTRIES_NAME_TOKEN where NAME is the name of the
registry in all capital letters.
The URL of the registry index to use.
No output printed to stdout.
Control when colored output is used. Valid values:
•auto (default): Automatically detect if
color support is available on the terminal.
•always: Always display colors.
•never: Never display colors.
May also be specified with the term.color config
If Cargo has been installed with rustup, and the first
argument to cargo
begins with +
, it will be interpreted as a
rustup toolchain name (such as +stable
). See the
for more information
about how toolchain overrides work.
Prints help information.
Unstable (nightly-only) flags to Cargo. Run cargo -Z
help for details.
•0: Cargo succeeded.
•101: Cargo failed to complete.
1.Yank a crate from the index:
cargo yank --vers 1.0.7 foo