-
Notifications
You must be signed in to change notification settings - Fork 599
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Add a dry-run publish API #1515
Comments
Reserved names would also be useful to catch with this; e.g. I got hit with
trying to publish my first crate, and had to dig pretty hard to find that it was part of the DB migration here |
If anyone has time to dig into this, now might be a good time to revisit this. We've been tracking some refactoring in #1522 and this may be easier to implement now. The goal is to make sure the desired checks are done early in the pipeline, before writing anything to the database. All database writes should occur after we return from the |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
In rust-lang/cargo#6150, @sfackler suggested that crates.io could have a dry-run publishing API endpoint, so it can enforce any requirements (like wildcard deps) in
cargo publish --dry-run
.I'd love to help out with that, if it's something worth doing.
The text was updated successfully, but these errors were encountered: