{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicb5w6wxhvimbkb6zpzrjxdt3utbmvhuexts77ddtuj56oesjozb4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mjkbdf7eim22"
  },
  "path": "/t/request-provide-an-official-way-to-deprecate-a-crate-not-yank-yank-is-stupid/24174#post_6",
  "publishedAt": "2026-04-15T14:50:46.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I guess where the deprecation metadata is actually stored can be flexible.\n\nHowever, regardless of where it is stored, I think it's important (in the user-facing side) that crate authors and maintainers don't have to go through any hoops or login to any 3rd-party services just to deprecate a package/version.\n\nThe crate author/maintainer should be able to run `cargo deprecate <PKG_NAME>[@<VERSION_RANGE>] -m <REASON>` as long as they have valid `token` on their `~/.cargo/credentials.toml`.\n\nAlternatively, they can just deprecate the packages/versions on the web UI of `crates.io`.",
  "title": "Request: Provide an official way to *deprecate* a crate. NOT yank. Yank is stupid"
}