{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifejkcctcu2z4tzk2s5xh47z7ucjygy3pldmfclz46dslry7a4yu4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mjppzmgg6ea2"
  },
  "path": "/t/request-provide-an-official-way-to-deprecate-a-crate-not-yank-yank-is-stupid/24174#post_16",
  "publishedAt": "2026-04-17T19:07:30.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I think that this should be a separate state (\"maintenance not required\") that is distinct from both maintained and unmaintained. I agree that a large number of crates, specially if they have little or no dependencies, are evergreen and require no maintenance.\n\nI think one trouble is that even crates that don't normally require maintenance may require it exceptionally (for example, a compiler bug was fixed but this crate was relying on it - if the crate owner is unresponsive, this should downgrade the crate from \"maintenance not required\" to \"unmaintained\")\n\nAnyway all such schemes for signaling maintenance should probably be opt-in. If the author does nothing, it should work as today.",
  "title": "Request: Provide an official way to *deprecate* a crate. NOT yank. Yank is stupid"
}