Changelog #109

There are some recent known issues related to the VS Code extension and the update mechanism:

• Since last week, users running VSCodium or another open-source build of Code might have issues opening projects. This is caused by a change to bundle the server binary with the extension, instead of downloading it on the first load. Unfortunately, Open VSX, which is the marketplace used by VSCodium and other forks does not support platform-specific, sometimes serving users binaries for the wrong platform. The workaround is to manually download the VSIX for your platform from GitHub releases, or to install the non-free version of Code.

• Since last Wednesday, if you install the rust-analyzer from Code, you might get an older version of the extension (0.2.853, from two weeks ago). This is caused by us publishing the nightlies as pre-release version to the Marketplace, which was done to avoid having to download VSIX updates from GitHub for users on the nightly channel. Unfortunately, after publishing the first pre-release version, the Marketplace stopped showing the latest stable version (0.2.867, from last week). The workaround is to manually download the VSIX from GitHub releases, or to switch to the pre-release version, then back to the stable one which appears to fix it, probably by triggering another Code bug.

• VS Code allows installing VSIX files that don’t match your platform. Please don’t do that.

• If you’re running a 32-bit version of VS Code on a 64-bit Windows system, please install the 64-bit version of Code instead. This configuration used to work thanks to a workaround in the extension (it downloaded the 64-bit binary), but it’s no longer supported. If you are actually running 32-bit Windows, you don’t need to do anything different since that’s not a supported platform anyway.

• It’s not yet known how updating between stable versions works.

If you’re not running one of the supported platforms, GitHub releases have a VSIX without an included server, but you’ll need to compile the server or obtain it by using rustup, just like before.

If you have any problems, please check the version you’re running against the one published on the Marketplace, check if you’ve set rust-analyzer.server.path (it’s not required on the supported platforms), and maybe file an issue if it still doesn’t work.