rust-lang / rust-lang/rust-analyzer
Outdated toolchain version error is hard to understand
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: 0.3.2711
rustc version: rustc 1.85.0 (4d91de4e4 2025-02-17)
editor or extension: VSCode
relevant settings: none
The message rust-analyzer produces when encountering an outdated toolchain version:
path/to/Cargo.tomlis using an outdated toolchain version 1.85.0 but rust-analyzer only supports 1.90.0 and higher. Consider using the rust-analyzer rustup component for your toolchain or upgrade your toolchain to a supported version.
... can be very confusing, especially if it suddenly starts appearing after VSCode has silently updated to a new rust-analyzer version that drops support for older toolchain versions (like 0.3.2711)
- It makes the user think their
Cargo.tomlis the issue - It's a bit unclear in how to resolve the issue (for someone unfamiliar with
rustup)
Better wording might be:
This project (
path/to/Cargo.toml) uses the Rust toolchain version 1.85.0, but rust-analyzer requires 1.90.0 or higher. You can update your toolchain by runningrustup update, or manually change overrides (if present).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search for the rust-analyzer diagnostic that emits the outdated toolchain message, then review how it is tested. Update the wording so it identifies the project toolchain rather than blaming Cargo.toml and explains rustup update or overrides as resolution paths. Done means the diagnostic is clearer and its tests cover the revised message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100