Rustup, the go‑to tool for installing and managing Rust toolchains, has just released version 1.29.0. This update brings significant performance improvements, broader platform support, and several quality‑of‑life enhancements. Below, we answer common questions about what’s new, how to upgrade, and what to watch out for.
What is the biggest improvement in rustup 1.29.0?
The headline feature of this release is the introduction of concurrent downloading and unpacking during operations like rustup update and rustup toolchain. Previously, components were fetched and extracted sequentially. Now, thanks to a Google Summer of Code project, rustup can download multiple components simultaneously and begin unpacking before all downloads finish. This dramatically reduces the time needed to update toolchains. The same concurrency applies to rustup check, which now checks for updates in parallel. While this is a major performance win, the change touches core parts of rustup, so users may encounter rare issues. The team encourages reporting any problems on the official repository.
Which new host platforms are now officially supported?
Rustup 1.29.0 adds official support for two additional host platforms: sparcv9-sun-solaris and x86_64-pc-solaris. This means users on Solaris systems (SPARC or x86‑64) can now install and manage Rust toolchains using rustup just like on Linux, macOS, and Windows. The inclusion of these platforms broadens rustup’s reach, especially for enterprise environments and legacy systems that rely on Solaris.
What new shells get automatic PATH entries during installation?
Rustup’s installer, rustup-init, can automatically add the necessary $PATH entries to your shell’s configuration file. With version 1.29.0, this automation now supports two additional shells: tcsh and xonsh. If you use either of these shells, running rustup-init will correctly update your environment so that Rust commands are available without manual configuration. This is in addition to the already supported shells like Bash, Zsh, Fish, and others.
How does rustup handle rust-analyzer now?
When you run rust-analyzer through a proxy (for example, via an editor integration), rustup will now look for a rust-analyzer binary in your PATH if the rustup‑managed version is not found. This change is especially useful for users who prefer to bring their own rust-analyzer binary — for instance, if you use editors like Neovim or Helix, or if you are developing rust-analyzer itself. It gives you more flexibility in managing which version of the language server is actually executed.
What changed with environment variable handling?
Rustup 1.29.0 now treats empty environment variables as unset. This means that if you have an override in your configuration and you set the corresponding environment variable to an empty string, rustup will treat that variable as not being set at all. The practical effect is that you can more easily reset configuration values back to their defaults — simply export an empty value instead of unsetting the variable. This simplifies scripting and configuration management.
How have the exit codes for rustup check changed?
The rustup check command now uses different exit codes to indicate whether updates are available. Specifically, it exits with code 100 if new updates were found and code 0 if everything is up‑to‑date. This change makes it easier to integrate rustup check into scripts and automation workflows — you can now detect whether an update is pending simply by checking the exit code.
Who joined the rustup team in this release?
We are thrilled to welcome FranciscoTGouveia as the newest member of the rustup team. Francisco demonstrated his talent, enthusiasm, and commitment from his very first interactions with the project. He played a significant role in bringing more concurrency to rustup, particularly in the concurrent downloading and unpacking feature that headlines this release. The team is excited to have him on board and looks forward to future contributions.
How do I update to rustup 1.29.0?
Updating is straightforward. If you already have rustup installed, close any programs that may be using it (such as your IDE) and run:
$ rustup self updateRustup will also automatically update itself at the end of a normal toolchain update ($ rustup update). If you don’t have rustup yet, you can get it from the official website. For detailed instructions, consult the rustup book.
Are there any caveats after upgrading?
As with any new release, some temporary issues may arise that are not caused by rustup itself. In particular, anti‑malware scanners might block rustup or prevent it from creating or copying files — especially when installing rust-docs, which contains many small files. These problems usually resolve automatically within a few weeks once the antivirus vendors update their definitions to recognize the new rustup build. If you experience unusual errors, try temporarily disabling your real‑time scanner or adding rustup to the exclusion list.