-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Bump cargo-vendor version #55363
Bump cargo-vendor version #55363
Conversation
It's be great to run a crater-equivalent and file issues against repositories with Cargo.lock files pinging cargo-vendor like this. |
@bors r+ |
📌 Commit 8b339b6 has been approved by |
Oh, also, we should not make this change on crates.io until stable Rust artifacts contain this change to ensure stable builds |
@bors r- Looking at the code a bit more, it might not be the cargo version. |
@Mark-Simulacrum I'm not 100% sure I understand what you mean by
|
@bors r=Mark-Simulacrum p=1 Confirmed this fixes the issue: cargo-vendor 0.1.4 pins cargo 0.16.0, which doesn't set an user agent. |
📌 Commit 8b339b6 has been approved by |
@sgrif right now the just-shipped 1.30 rust artifacts don't contain this PR which I think might make it such that distros would be unable to build in some cases if we made the change to crates.io; basically, ideally we'd wait until 1.31 ships to make that change. Does that help? |
@Mark-Simulacrum So the concern is for distros that build from source? |
…acrum Bump cargo-vendor version to 0.1.17 Currently we pin `cargo-vendor` to 0.1.4, which doesn't set the `User-Agent` HTTP header. crates.io is going to require that header in the near future, so this PR bumps the pinned version of the crate to the latest one (which correctly sets the header). r? @Mark-Simulacrum cc @sgrif
💔 Test failed - status-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors r- Looks like it doesn't work 😕 |
RUSTC_BOOTSTRAP isn't enough because Cargo uses a different environment variable, IIRC. |
Ok, I don't think I can solve this.
The problem we're having right now is that Clippy removed the feature gate from its What should we do?
Cargo also reads |
Feel free to add the gate to clippy again |
eab9e7e
to
eee136c
Compare
This is blocked on alexcrichton/cargo-vendor#138. |
eee136c
to
4084eb0
Compare
Bumped cargo-vendor to 0.1.19: it's now using Cargo 0.31.0 (with stable |
@bors r+ |
📌 Commit 4084eb0 has been approved by |
@bors p=0 Not critical to get this merged as soon as possible, since the crates.io team is not implementing this change right now (and it might not affect us anyway if they continue to allow downloads without an user agent). |
…acrum Bump cargo-vendor version Currently we pin `cargo-vendor` to 0.1.4, which doesn't set the `User-Agent` HTTP header. crates.io is going to require that header in the near future, so this PR bumps the pinned version of the crate to the latest one (which correctly sets the header). r? @Mark-Simulacrum cc @sgrif
☀️ Test successful - status-appveyor, status-travis |
Currently we pin
cargo-vendor
to 0.1.4, which doesn't set theUser-Agent
HTTP header. crates.io is going to require that header in the near future, so this PR bumps the pinned version of the crate to the latest one (which correctly sets the header).r? @Mark-Simulacrum
cc @sgrif