Why does the rust-analyzer VS Code extension insist on being out-of-date?
I can not get a version of the rust-analyzer extension more recent than ~7 months out of date. I see that the latest version is 0.3.2020 and yet when I install the extension and reload VS Code, it has installed 0.3.1730. The rust-analyzer changelog says this version was released 2023-11-13.
Pre install:
Post install:
Accessing the "Uninstall" dropdown and selecting "Install Another Version..." yields a list with seemingly all versions 0.3.1730 and prior. Trying to manually enter in "0.3.2020" results in an empty list and pressing Enter does nothing.
There is a pre-release channel which should have 0.4.2023 as the latest version, but installing it gives me 0.4.1731. Trying to "Install Another Version..." there was similarly fruitless.
Trying to install a version downloaded directly from the marketplace just yields an error "One or more extensions are for Visual Studio Code. Try installing them in Visual Studio Code." Not helpful.
This is fairly important because rust-analyzer should be relatively in-sync with the Rust version you're using. With them out-of-sync, the user experience is pretty poor mostly due to errors with proc-macro evaluation. But obviously to make them in-sync requires downgrading my Rust version which I would like to avoid.
I have looked at rust-analyzer specific issues and have not noticed anyone else reporting these symptoms. So I feel it is likely an issue with my setup but I don't know how to debug the behavior.
I am on Windows 10. VS Code version 1.77.0. I don't seem to have an issue with other extensions.
Update VS Code.
When finishing up the question above, I found that 1.77.0 is very out of date (March 2023 release was ~16 months ago). Updating to the latest 1.91.0 allowed the latest version of rust-analyzer to be installed.
I had apparently disabled updates at some point and just never noticed over the past year. I would've liked some kind of "latest version could not be installed due to ..." warning, but I'm guessing this scenario is not common.
- Use fvm to change flutter version in vscode, but the flutter version not work?
- React & VsCode forwardRef Intellisense
- VS Code terminal doesn't recognize PATH variables
- How to remove that tree structure at the top on Visual Studio?
- in vscode, can I open a directory in the current window via the terminal/cli
- How to remove Incoming/Outgoing changes graph in VSCode?
- VS Code Sync Changes: Always pushes to master
- Mac OS - Run VS Code with admin privileges so the changes can be applied
- vscode spends long time beginning to run the python file
- VS Code 1.94 - Run selection/line in Python terminal very slow
- How to quickly change shell folder to match the currently open file
- How can I use VS Code to update extensions via commandline?
- Why is my VS Code always opened with the default profile?
- How to disable "just my code" setting in VSCode debugger?
- Node.js does not read env variable set in Mac native Terminal
- VSCode does not update environment variables upon .env modification
- How do I remap the `Alt+Click` action in visual studio code?
- VScode equivalent of Jetbrains/IntelliJ/Rubymine scratches (throwaway notes)
- Extension 'eslint' is configured as formatter but it cannot format 'JavaScript'-files
- What exactly is Visual Studio Code?
- Visual Studio Code: Auto-refresh file changes
- VSCode Zen Mode: Extend Editor Width (Remove Side Margins)
- How to find-and-replace in Visual Studio code in just the selection (selected text)?
- Disable annoying source code modification indication (codelenses and text decorations)
- pyvisa script only works when stepping through code
- Organise imports for all files in project
- How to hide the bottom panel, no matter which tab I'm on?
- How to sign out github account in vs code
- Is there a way to remove unused imports for Python in VS Code?
- VSCode Code Spell Checker extension - include .todo files