Add a way to delete a crate that recently (~2 year ago) became obsolete #12812
wvwwvwwv
started this conversation in
Feature Requests
Replies: 1 comment 5 replies
-
|
this policy is an intentional choice to ensure that older revisions of Rust projects can still be built |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
E.g., I uploaded https://crates.io/crates/async-trait-fn for ergonomic stack-allocated
impl Futureusage in a trait, but it has become completely obsolete as soon as Rust 1.75 was released (async fn / -> impl Trait). Now, no GitHub projects use the crate, and no crates depend on async-trait-fn, but I cannot delete this crate since the crate was downloaded ~400K times in the past; I would be able to delete this crate after 30 years...Therefore, I would suggest crates.io allow crate owners to delete a crate IF the crate has not been downloaded more than 1000 times per month "for the past 2 years".
Beta Was this translation helpful? Give feedback.
All reactions