-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[1.30 beta] Multiple applicable items in scope #54474
Comments
|
All of these are binaries with checked in lockfiles that depend on a petgraph version |
As the author of the one of the impacted crates, opening an issue like this and tagging me seems like a good protocol. My crate is linked to the Dependabot service so I'm curious to wait and see if it will flag the update to the new petgraph as an important one. |
As the author of one of the impacted repositories I appreciate this protocol a lot too. Although in this particular case my repo contains some unimportant stuff so I don't mind it breaking. |
This was added in #49098 and stabilized in #53385. Unfortunately we didn't do crater runs at the time, but that's why we do it for beta! I'll put this on the libs team triage agenda, but given that this is fixed in the most recent versions and only locked projects are getting this it's probably unlikely we'll decide to revert. That being said if anyone has difficulty upgrading please let us know! |
Ok discussed during triage and we've decided to close, but again anyone please let us know if it's difficult to update! |
Multiple crates are failing to build in 1.30 beta because multiple applicable items are in scope.
cc @petrochenkov
The text was updated successfully, but these errors were encountered: