Cargo incorrectly identifies transitive dependency versions when compiling new dependencies about cargo HOT 3 CLOSED

Tried to simplify the reproduction steps

$ cargo new cargo-14059
$ cd cargo-14059
$ cargo add moka@=0.12.5 -Fsync,future
$ cargo check
$ git add . && git commit -m "Initial"
$ cargo add chewdata@=2.11.0
$ cargo check

However, this did not reproduce the problem with Cargo 1.79.

from cargo.

$ git checkout HEAD~
$ rm Cargo.lock
$ cargo +1.77 check
$ git diff

and the lockfile was unchanged

$ git checkout main
$ git checkout HEAD~ -- Cargo.lock
$ cargo +1.77 check
$ git add .
$ git status

and the build worked and the lockfile was unchanged

from cargo.

@epage I looked further into this, and it seems the issue was with async-channel 2.3.0 having the wrong dependency bounds. This was fixed in 2.3.1, and I think we just hit a weird edge case when that change was made relative to our existing lockfile. Trying again with the more limited case in a fresh project also did not replicate for me.

My apologies for the noise on this. I'll go ahead and close this as resolved in the original project.

from cargo.