-
Notifications
You must be signed in to change notification settings - Fork 13.4k
cargo-fmt
reports weird version on nightly
#137666
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I did a quick check, #137541 doesn't fix this. |
Clippy doesn't have this problem. Since both tools share common implementations I assume there might be some internal logic in |
It has been fixed?
|
I still see this:
|
Try to update the nightly?
|
No it is updated :) That's why it's super weird. I also removed the toolchain and reinstalled it.
I even tried a pinned nightly (2025-03-01) which doesn't have any extra components, where the same thing happens. |
The code is here. It seems that |
I tried it just now and it seems to be working as expected: $ ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin $ ./rustfmt --version
rustfmt 1.8.0-nightly (414482f6a0 2025-05-13)
$ ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin $ ./cargo-fmt --version
rustfmt 1.8.0-nightly (414482f6a0 2025-05-13) |
~$ ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustfmt --version
rustfmt 1.8.0-nightly (414482f6a0 2025-05-13)
~$ ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/cargo-fmt --version
rustfmt 1.8.0-stable (05f9846f89 2025-03-31) Not sure why is there a difference between your and my environment :/ |
lol this is weird |
I found the problem and explained it in the fix PR. |
The version has a different date than
rustfmt
, which I would perhaps understand, but it's a bit weird that it says-stable
even though it's in the nightly toolchain.It's possible that #137541 might fix this, we'll see after the next nightly is released.
The text was updated successfully, but these errors were encountered: