-
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
Update Cargo #50135
Update Cargo #50135
Conversation
Some noteble changes: * regression fix: rust-lang/cargo#5390 * potentially breaking bug-fix: rust-lang/cargo#5389 * Cargo now caches the result of `rustc -vV`. It checks `rustc` binary mtime and rustup toolchain settings, so it should probably "just work" with rustbuild.
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
I don't see anywhere in the diff related to this. If you mean rust-lang/cargo#5389 it is already included by #50056. |
@kennytm oh, indeed! Looks like 2 of 3 points are actually already here, updated the description! |
@bors r+ |
📌 Commit cb46d28 has been approved by |
Update Cargo Some noteble changes: * ~~regression fix: rust-lang/cargo#5390 * ~~potentially breaking bug-fix: rust-lang/cargo#5389 * ~~Cargo now caches the result of `rustc -vV`. It checks `rustc` binary mtime and rustup toolchain settings, so it should probably "just work" with rustbuild.~~ potentially breaking bug-fix: rust-lang/cargo#5390
☀️ Test successful - status-appveyor, status-travis |
Some noteble changes:
regression fix: Enable new behavior of--feature
cargo#5390potentially breaking bug-fix: One hard cs problem cargo#5389Cargo now caches the result ofrustc -vV
. It checksrustc
binarymtime and rustup toolchain settings, so it should probably "just work"
with rustbuild.
potentially breaking bug-fix: rust-lang/cargo#5390