rustup 1.29.0: Key Updates and Answers to Your Questions
Discover rustup 1.29.0's concurrent downloads, new Solaris support, tcsh/xonsh PATH integration, rust-analyzer proxy handling, and exit code changes. Includes update instructions and known caveats.
Welcome to the latest release of rustup, version 1.29.0! This update brings significant performance boosts, broader platform support, and several quality-of-life improvements. Below, we answer the most common questions about what's new, how to update, and what to watch out for. Jump to the concurrency feature or explore each topic below.
What's the biggest performance improvement in rustup 1.29.0?
The headline feature is that rustup can now download components concurrently and unpack them during downloads for operations like rustup update or rustup toolchain install. Additionally, rustup check benefits from concurrent update checks. This change, made possible by a GSoC 2025 project, dramatically reduces the time needed to install or update toolchains. While this is a complex change, the team has tested it thoroughly, but if you encounter any issues, please report them on the rustup repository.
Which new host platforms does rustup 1.29.0 support?
Rustup now officially supports two Solaris platforms: sparcv9-sun-solaris and x86_64-pc-solaris. This expands rustup's reach to users on Sun Solaris systems, allowing them to easily install and manage Rust toolchains on both SPARC and x86 architectures. If you're on Solaris, you can now use rustup just like on Linux, macOS, or Windows.
Are there improvements for shell integration?
Yes! Rustup now automatically inserts the correct $PATH entries during rustup-init for two additional shells: tcsh and xonsh. Previously supported shells (bash, zsh, fish, etc.) continue to work as before. This means tcsh and xonsh users will have a smoother setup experience when installing Rust for the first time.
How does rustup 1.29.0 change rust-analyzer handling?
When running rust-analyzer through a proxy, rustup now looks for the rust-analyzer binary from PATH if the rustup-managed one isn't found. This is especially useful if you use editors like Neovim or Helix and prefer to bring your own rust-analyzer build—perhaps because you're developing the analyzer itself. The change ensures that rustup doesn't block custom binaries while still supporting the default setup.
What changes were made to environment variables and exit codes?
Two subtle but helpful improvements: Empty environment variables are now treated as unset, making it easier to reset configuration defaults when an override is present. Also, rustup check now uses distinct exit codes: 100 if updates are available, 0 if not. This allows scripts and automation to react differently based on whether updates exist.
How do I update to rustup 1.29.0 and are there any known issues?
If you already have rustup installed, simply run rustup self update (after closing any programs using rustup) or let rustup auto-update with rustup update. New users can download it from the official website. One caveat: anti-malware scanners may temporarily flag the new release, causing installation failures for large docs packages. This usually resolves within a few weeks as scanners update their databases. For full details, consult the changelog. Also, welcome to the new team member FranciscoTGouveia, who contributed heavily to the concurrency feature!