We are excited to announce that rustup 1.29.1 beta is now available for testing and we are currently looking for testers.

What's new

The headlines of this release are:

• Concurrency in certain rustup operations has been improved:

  • When running rustup update, rustup will first check for possible updates in parallel. pr#4752
  • When running rustup component add with multiple components, they will be installed concurrently. pr#4790

• Implicit installation of the active toolchain in rustup-init and rustup invocations has been deprecated where deemed unnecessary and will now produce a warning. pr#4840

  • Please see our blog post for more details regarding this change.

• Installing i686-pc-windows-* host toolchains on 64-bit Windows now requires --force-non-host. pr#4935

• A bug has been fixed which might cause Windows installation to fail when using rustup-init.sh. pr#4756

• "Target triple" has been renamed to "target tuple" across the project to reflect the new terminology. pr#4743 pr#4827 pr#4834

  • Please note that this is not a breaking change in the CLI since the existing options such as --target are not using this terminology.

In addition, rustup now officially supports aarch64-pc-windows-gnullvm as a host platform. pr#4523

Further details are available in the changelog!

As usual, we would be happy to receive regression/breakage reports of any kind.

How to test

To begin testing this new version, all you need to do is simply switching to the dev environment by setting the following environment variable when updating or installing rustup:

RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup

To switch out of the dev environment, just remove that environment variable and do a rustup self update.