Skip to content

Crate deletion allowances#3927

Open
clarfonthey wants to merge 2 commits intorust-lang:masterfrom
clarfonthey:deletion-allowances
Open

Crate deletion allowances#3927
clarfonthey wants to merge 2 commits intorust-lang:masterfrom
clarfonthey:deletion-allowances

Conversation

@clarfonthey
Copy link

@clarfonthey clarfonthey commented Mar 12, 2026

This RFC proposes adding a number of "reasonable changes" to the current crates.io deletion policy that will allow the deletion of several "reasonable to delete" crates which currently do not qualify.

They are definitely, directly, shamelessly motivated by the personal experience of the RFC author. Please let them know if anything was poorly or hastily worded.

Important

When responding to RFCs, try to use inline review comments (it is possible to leave an inline review comment for the entire file at the top) instead of direct comments for normal comments and keep normal comments for procedural matters like starting FCPs.

This keeps the discussion more organized.

Rendered

@clarfonthey clarfonthey changed the title Add crate deletion allowances RFC Crate deletion allowances Mar 12, 2026
* or if all the following conditions are met:
* The crate has a single owner,
* The crate has been downloaded less than 100 times for each month it has been published,
* The crate is not depended upon by any other crate on crates.io (i.e. it has no reverse dependencies), excluding yanked versions of crates that were published over a year ago
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the proposed changes it becomes important to specify whether this is a direct or a transitive dependency.

(eg. consider [regular crate] -> [yanked crate] -> [crate to be deleted])

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I decided to just elaborate this section more fully to make it clearer; what do you think now?

@ehuss ehuss added the T-crates-io Relevant to the crates.io team, which will review and decide on the RFC. label Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-crates-io Relevant to the crates.io team, which will review and decide on the RFC.

Projects

Status: For next meeting

Development

Successfully merging this pull request may close these issues.

4 participants