-
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
Bump nightly version to 1.52.0 #81792
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ rollup=never |
📌 Commit c51e432 has been approved by |
⌛ Testing commit c51e432 with merge fa79c8ba8f9acbde2784368b71d7d2e905343f82... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@rust-lang/clippy -- it looks like this is a new test added to ensure clippy's version matches rustc's -- for now, can someone provide instructions on the right set of steps to take? In the future it would be great to ping me / release team if you're adding tests that are affected by version numbers and might cause problems during our release cycle. If we don't hear back by Saturday evening I'm probably going to just disable these tests for now since we need this PR to land. |
Sorry about that, this is my fault. Test location: https://github.com/rust-lang/rust-clippy/blob/master/tests/versioncheck.rs Basically with rust turning If you bump the versions (in the subrepo) at |
a5ac5b7
to
83c34ea
Compare
@bors r+ rollup=never Thanks. I've opened rust-lang/rust-clippy#6683 to track discontinuing this requirement upstream. |
📌 Commit 83c34ea has been approved by |
☀️ Test successful - checks-actions |
cc @rust-lang/release