Source-backed platform rule

crates.io yanked-version resolution behavior

Cargo excludes a yanked version from default new dependency resolution while leaving its data, direct download, and existing-lockfile behavior intact.

RuleRoster is independent and is not affiliated with or endorsed by crates.io.

Direct answer

What is the rule?

Yanking a crates.io version prevents Cargo from selecting it during dependency resolution by default, but does not delete data, block direct downloads, or affect existing lock files. Resolution errors if no compatible versions remain.

Scope: crates.io package publishing, names, permanence, and yanking
Human verified: August 14, 2026
Source checked: September 3, 2026

Published evidence

Rule details

Yanked-version behavior

Yanking prevents Cargo from selecting the version during dependency resolution by default. It removes the version from the server index but does not delete data; direct downloads remain available and existing lock files are unaffected. Cargo errors when no compatible versions remain. Yanking is not credential recall or source deletion.

Applicability

Service: crates.io. Rule group: dependency selection. Scope: default selection of a yanked version, existing lock files, and direct downloads. Policy version and effective dates: not stated.

Evidence trail

Official sources

Cargo Book crates.io yanked-version resolution behavior
crates.io · verified August 14, 2026

Attribution and license

Cargo Book by The Rust Project Developers. Source: https://github.com/rust-lang/cargo/tree/83b31e5eff16b42e4810b7affd7a07c5a1f444b2. Licensed under Apache License 2.0: https://github.com/rust-lang/cargo/blob/83b31e5eff16b42e4810b7affd7a07c5a1f444b2/LICENSE-APACHE. Modified by RuleRoster: RuleRoster extracted and restructured facts into typed rule fields and concise answers. Verified 2026-08-14. No endorsement by the Rust project, Cargo, or crates.io is implied. Project names and marks remain descriptive source identifiers only.

Interpretation and accountability

Before you act

Confirm that the scope matches your case.
Keep recommendations, enforced limits, exceptions, and unstated details distinct.
Open the official source before relying on the rule for a consequential decision.

Record dates

Published: August 15, 2026
Human verified: August 14, 2026
Source checked: September 3, 2026
Review due: September 10, 2026

Challenge this record

If the source or summary appears wrong, submit precise evidence for human review.

Submit a correction