You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clippy has been on version 0.0.212 for quite some time now, and the version number has become quite irrelevant now that we always ship a -git version with nightly/beta/stable.
Should we pin the clippy to the respective rustc version like cargo does?
cargo 0.49.0 corresponds to rustc 1.49.0.
Equally, we could bump clippy to 0.1.49 for beta, and 0.1.50 for nightly.
The text was updated successfully, but these errors were encountered:
make clippy version number correspond to rustc version number.
clippy 0.1.50 corresponds to rustc 1.50.x
This bumps the clippy version number from 0.0.212 to 0.1.50
Fixes#6499
Notes:
I used `cargo --version` because that way we can honour the version set in the `rust-toolchain` file.
When we bump the bootstrap compiler from 1.50 to 1.51, the version numbers will have to be changed to 1.51 or the test will fail.
---
changelog: make clippy version number correspond to rustc version number (rust 1.50.0 -> clippy 0.1.50)
Clippy has been on version
0.0.212
for quite some time now, and the version number has become quite irrelevant now that we always ship a-git
version with nightly/beta/stable.Should we pin the clippy to the respective rustc version like cargo does?
cargo 0.49.0 corresponds to rustc 1.49.0.
Equally, we could bump clippy to 0.1.49 for beta, and 0.1.50 for nightly.
The text was updated successfully, but these errors were encountered: