Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow deletion of crates within 24 hours of publishing #5293

Closed
carols10cents opened this issue Oct 7, 2022 · 7 comments
Closed

Allow deletion of crates within 24 hours of publishing #5293

carols10cents opened this issue Oct 7, 2022 · 7 comments
Labels
A-backend ⚙️ B-needs-rfc C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works

Comments

@carols10cents
Copy link
Member

NPM has this policy to better handle accidental publishing.

@Turbo87
Copy link
Member

Turbo87 commented Oct 8, 2022

@carols10cents did you mean to say "Allow deletion of crate versions"? At least that is what I would expect 😅

@carols10cents
Copy link
Member Author

Well if you create the only version of a crate, then I think people would expect the entire crate would be deleted and available for someone else to claim again, right?

@Turbo87
Copy link
Member

Turbo87 commented Oct 9, 2022

yes, that would be the consequence :)

@Turbo87 Turbo87 added C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works A-backend ⚙️ B-needs-rfc labels Oct 9, 2022
@ThrashAbaddon
Copy link

I like this. For every package in the company we have publish = false in Cargo.toml for just in case.

@wildwestrom
Copy link

I think it's a good idea. Pretty harmless.
You can't be that invested in a crate if you just depended on it within 24 hours of publishing.

@Turbo87
Copy link
Member

Turbo87 commented Jun 22, 2024

@Turbo87
Copy link
Member

Turbo87 commented Oct 2, 2024

the above RFC has been accepted and merged, and #9352 is now open as a tracking issue for the implementation. since this is essentially a duplicate of this issue I'll close this one now in favor of the official tracking issue :)

@Turbo87 Turbo87 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ B-needs-rfc C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants