Rustup 1.29.0 Arrives With Concurrent Downloads and Expanded Platform Support

The rustup team shipped version 1.29.0 on March 12, 2026, and the headline change is one that anyone who has sat watching a sequential toolchain install grind through components will immediately appreciate: rustup can now download components concurrently and unpack them during the download process, rather than waiting until each fetch completes before moving on.

The concurrency work came out of a GSoC 2025 project and was implemented primarily by @FranciscoTGouveia, with contributions from @djc across multiple PRs including pr#4426, pr#4436, pr#4471, and pr#4605. The improvement touches the two subcommands where you feel slowness most acutely: `rustup update` and `rustup toolchain`. Progress bars have been updated to reflect the parallel activity and give better feedback about where time is actually being spent. If the default concurrency level doesn't suit your setup, the `RUSTUP_CONCURRENT_DOWNLOADS` environment variable lets you tune it. The team's own note on the blog is worth taking seriously: "This is by no means a trivial change so a long tail of issues might occur, please report them if you have found any!"

`rustup check` also gained concurrency for update checks, and now exits with code 100 when updates are found and 0 when there are none, making it much more useful in scripting contexts where you want to branch on whether a toolchain update is available.

On the platform side, rustup 1.29.0 officially adds host support for sparcv9-sun-solaris and x86_64-pc-solaris. Shell coverage expanded as well: `rustup-init` will now automatically insert the correct `$PATH` entries for tcsh and xonsh, in addition to the shells it already handled.

Several quality-of-life fixes round out the release. When rust-analyzer is invoked via a rustup proxy but no rustup-managed binary is found, rustup will now fall back to whatever `rust-analyzer` is on your PATH rather than failing outright. Empty environment variables are treated as unset, which cleans up edge cases where you might have an override set to an empty string and expected default behavior. Color and styling output received a round of fixes from @epage, aligning `rustup check`, `rustup update`, and the list and show subcommands more closely with how Cargo renders its own output, including respecting the `RUSTUP_TERM_COLOR` variable.

@FranciscoTGouveia also officially joined the rustup team with this release. The blog announcement described his role plainly: "He has shown his talent, enthusiasm and commitment to the project since the first interactions with rustup and has played a significant role in bring more concurrency to it, so we are thrilled to have him on board."

Updating is straightforward: close any programs that might be holding rustup open, such as your IDE, then run `rustup self update`. The changelog is dated 2026-03-05 in the repository, with the public blog announcement following on March 12, 2026.