Closed smoelius closed 9 months ago
Looks like the same bug: https://github.com/rust-lang/cargo/issues/13002
(I probably should have opened this issue on the Cargo repo.)
This fails for us in Bevy's CI too: https://github.com/bevyengine/bevy/actions/runs/6921162111/job/18826441217#step:5:537
It's due to the upstream issue mentioned above. TLDR they did semver breaking changes and only incremented the patch version.
There is an upstream PR: https://github.com/rust-lang/cargo/pull/13004
I'm wondering what to do here:
Do you think it's worth to cut a release just for this?
Do you think it's worth to cut a release just for this?
IMHO, it is fine to wait for the problem to be fixed upstream.
I apologize for making noise on your repo about a problem that is not yours.
https://github.com/rust-lang/cargo/pull/13004 was just merged
https://github.com/rust-lang/cargo/issues/13002#issuecomment-1820290411
The problem as I reported it no longer applies. Closing.
Cloning
cargo-udeps
and runningcargo update -p cargo-credential-libsecret && cargo check
produces the output below. (Right now, crates.io tells mecargo-credential-libsecret
is about three hours old.)