-
Notifications
You must be signed in to change notification settings - Fork 607
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
Point out which crates have a wildcard version that isn't allowed #6827
Comments
I'm happy to help anyone who wants to take this one on. Here's where the code needs to change:
And actually, in the issue description, I was envisioning that if multiple dependencies had this problem, we'd list them all. However, this code collects all the |
Ah, that issue already exists 😅 #3054 |
Hey, I could like to try this. |
Created #6829 for this. Please take a look when have the time. Thanks! |
Current Behavior
A user tried to publish a crate with this
Cargo.toml
:`Cargo.toml` content
and got this error:
Can you spot the problem? How long did it take you?
Answer
The problem was this line:
that had
ver
instead ofversion
, which is interpreted as "no version" or "wildcard" by crates.io.Expected Behavior
If crates.io instead returned an error like this, pointing out which crate or crates in the list of dependencies was causing the problem:
it would be a lot easier to figure out what the problem was.
Steps To Reproduce
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: