-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
codegen: Remove yanked crate #549
Comments
While yanked versions should not be selected in the latest and omitted versions (this is already implemented), I don't think they should be disallowed from being used when explicitly specified. As far as I know, cargo is also moving in that direction: rust-lang/cargo#13974 |
Thanks, yeah I can understand that decision. In that case, how about storing the yanked information in manifest, and then default to skip the yanked version, while allowing user to override that behavior? |
Unless you explicitly specify the full version ( |
I think it is good to warn if the yanked version is explicitly selected, but I don't think we should change the version on our own. |
Thank you! |
In the cronjob, we could check for yanked crates and remove them from this action.
The text was updated successfully, but these errors were encountered: