Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
treewide: fix cargoSha256 (again) #76060
Motivation for this change
This time the change in
I hope that some time soon we can ban
Why did the rustc update cause `cargo vendor` output to change though? What's the root cause here?
It looks like Cargo.lock files are no longer excluded. So only the packages with dependencies containing Cargo.lock would have changed. At least, that's what's changed for the one I looked at (rsclock, whose vendored autocfg now includes Cargo.lock).
Wow really? That seems really odd, because I thought Cargo.lock was intentionally and explicitly excluded from dependencies.
Yep. You can confirm yourself by building rsClock.cargoDeps before that commit was merged from staging-next, and after, and comparing with diffoscope. It might not be that Cargo.lock specifically is now included, though. Maybe there was some other change to inclusion logic made that just happened to manifest as Cargo.lock beginning to be included in this case.