Posts tagged "rustup" | Rust Blog

Announcing rustup 1.29.2

2026-10-20T00:00:00+00:00

The rustup team is happy to announce the release of rustup version 1.29.2.

Rustup is the recommended tool to install Rust, a programming language that empowers everyone to build reliable and efficient software.

What's new in rustup 1.29.2

This is a small release which only updates the rustls-webpki and webpki-root-certs dependencies to address the problematic eMudhra intermediate certificates issue described in CVE-2026-111943.

How to update

If you have a previous version of rustup installed, getting the new one is as easy as stopping any programs which may be using rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

If you don't have it already, you can get rustup from the appropriate page on our website.

Rustup's documentation is also available in the rustup book.

Caveats

Rustup releases can come with problems not caused by rustup itself but just due to having a new release.

In particular, anti-malware scanners might block rustup or stop it from creating or copying files, especially when installing rust-docs which contains many small files.

Issues like this should be automatically resolved in a few weeks when the anti-malware scanners are updated to be aware of the new rustup release.

Thanks

Thanks again to all the contributors who made this rustup release possible!

Announcing rustup 1.29.1

2026-09-01T00:00:00+00:00

The rustup team is happy to announce the release of rustup version 1.29.1.

Rustup is the recommended tool to install Rust, a programming language that empowers everyone to build reliable and efficient software.

What's new in rustup 1.29.1

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.
rustup doc now supports the --serve flag which allows serving the docs over local HTTP. This should help users with containerized browser and/or rustup setups. pr#4986
Installing i686-pc-windows-* host toolchains on 64-bit Windows now requires --force-non-host. pr#4935
rustup-init will no longer leave unexpected files on disk after cancelled installations. pr#4996
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!

How to update

If you have a previous version of rustup installed, getting the new one is as easy as stopping any programs which may be using rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

If you don't have it already, you can get rustup from the appropriate page on our website.

Rustup's documentation is also available in the rustup book.

Caveats

Rustup releases can come with problems not caused by rustup itself but just due to having a new release.

In particular, anti-malware scanners might block rustup or stop it from creating or copying files, especially when installing rust-docs which contains many small files.

Issues like this should be automatically resolved in a few weeks when the anti-malware scanners are updated to be aware of the new rustup release.

Thanks

Thanks again to all the contributors who made this rustup release possible!

Rustup 1.29.1 beta: call for testing!

2026-07-14T00:00:00+00:00

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.

Rustup update: our plans for the 1.30 release cycle

2026-07-03T00:00:00+00:00

This blog post is t-rustup's first attempt of providing a more transparent view of the team's current work.

Here, we summarize the focus areas of t-rustup in the ongoing release cycle leading to the future 1.30.0 release, hoping to inform you of our future plans, and ask for your feedback to help us make rustup better.

Ongoing Changes

Refining the implicit installation behavior

In rustup 1.27 or earlier, rustup would implicitly install the active toolchain once found missing whenever rustup is invoked, including proxy invocations such as rustc and cargo. There wasn't a way to disable this behavior, and it had become a source of confusion from time to time.

Back when rustup 1.28.0 was released, implicit installation has been entirely removed, which was a significant change in behavior that wasn't well communicated to users, and we would like to sincerely apologize for the frustration this has caused.

In response to this breakage, implicit installation has been re-enabled, and you can control it with the RUSTUP_AUTO_INSTALL environment variable or the rustup set auto-install command.

However, it does seem that this behavior would be clearly unnecessary in certain places, such as in the following example with rustup 1.27.1, where rustup must install the active toolchain before removing a target while it should have bailed out:

> rustup --version
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.81.0 (eeb90cda1 2024-09-04)`

> rustup +beta target remove aarch64-apple-darwin
info: syncing channel updates for 'beta-aarch64-unknown-linux-musl'
1007.6 KiB / 1007.6 KiB (100 %) 567.4 KiB/s in  1s ETA:  0s
info: latest update on 2025-09-28, rust version 1.91.0-beta.4 (aa7859c0d 2025-09-27)
info: downloading component 'cargo'
^C

To make sure that rustup is not doing unnecessary work, we would like to disable implicit installation of the active toolchain in the rustup-init and rustup invocations when unnecessary starting from 1.30. You can refer to the issue for a complete list of impacted subcommands.

With the new behavior, the above example would simply fail, which should feel more natural:

> rustup +beta target remove aarch64-apple-darwin
error: toolchain 'beta-aarch64-unknown-linux-musl' is not installed
...

To avoid further confusions, we would like to stress a few points regarding this change and its potential impact:

Since we're PRESERVING implicit installation on proxy invocations like rustc and cargo, this should not cause widespread breakage as seen when 1.28.0 was released.
Most cases where rustup-init or rustup are invoked don't require the active toolchain to be implicitly installed, so we expect the disruption caused by this change to be minimal.
Instead of using commands like rustup show to trigger toolchain installation, we recommend using rustup install instead.
In future 1.29 releases, upon triggering implicit installation in any of the relevant rustup subcommands, rustup will print a deprecation warning to inform you of the upcoming change.

If you still have any concerns regarding the above change, please let us know in the issue thread.

Simplification of download & TLS backends

Since a long time ago, the simplification of the rustup codebase has been a recurring topic for the team. One particular area of interest is the downloader subsystem, since supporting the combination of different download and TLS backends has been a source of significant maintenance burden.

So far, we have made significant progress towards establishing the new defaults: the reqwest download backend and the rustls TLS backend have been the default and recommended choice since 2019 and 2025 respectively, and starting from 2025, the uses of the deprecated curl download backend and the native TLS backend have been triggering deprecation warnings.

In this release cycle, we have decided to take the next step in this effort by removing the curl download backend. This change has recently been merged and is planned to be shipped in the 1.30 release which is expected to happen in 4 to 8 months.

In addition, the native TLS backend has also been a difficult subject for the team especially due to the difficulties of building and/or linking OpenSSL consistently across multiple platforms. There are currently no plans to remove it notably due to Linux packaging policies, but it might be downgraded to "guaranteed to build" support from a certain point on in the future.

We encourage you to switch to the reqwest download backend and the rustls TLS backend if you haven't already done so (if you haven't seen any related deprecation warnings, you have nothing to worry about!). If there are specific reasons preventing you from making the switch, please let us know via an issue and link to the previous CfT.

To Be Worked on Shortly

Below is a list of the things that the team plans to work on in the near future:

XDG Paths Support: This is our GSoC 2026 Project.
Notify users of possible updates
Signing & mirroring support

Focus Areas Without Progress

Below is a list of objectives on the team's radar where progress has been limited:

Artifact signing
Process safety
Toolchain identification & deduplication
Toolchain content verification & repair
Enhanced concurrency in toolchain installation
MSVC environment setup improvements
JSON output mode
Trusted directories

Contributions Welcome

Restriction of toolchain names

In the past, rustup used to put nearly no restrictions on toolchain names, which led to a lot of unnecessary complexities. Notably, this has caused some phishing concerns and has also prevented us from allowing certain toolchain names to bear a special meaning.

To improve the current situation, we are planning to restrict toolchain names so that they should appear less surprising in the future, and that some particular formats can be reserved for special purposes.

In fact, the team has made the first step in 1.29 by disallowing toolchain names that start with + and the outcome seems to be positive so far.

If you are interested in helping us out with this effort, please reach out at the issue thread so that we can work out the details and the next steps together.

How You Can Help

You can help us out by participating in the project's development in different ways, such as providing feedback on the ongoing changes or helping us out with the issues we think would be a fit for interested contributors in the "Contributions Welcome" section.

In addition, if there is a specific issue not discussed here that you are interested in addressing but you are not sure of what to do, please don't hesitate to reach out to our Zulip channel.

Announcing rustup 1.29.0

2026-03-12T00:00:00+00:00

The rustup team is happy to announce the release of rustup version 1.29.0.

Rustup is the recommended tool to install Rust, a programming language that empowers everyone to build reliable and efficient software.

What's new in rustup 1.29.0

Following the footsteps of many package managers in the pursuit of better toolchain installation performance, the headline of this release is that rustup has been enabled to download components concurrently and unpack during downloads in operations such as rustup update or rustup toolchain and to concurrently check for updates in rustup check, thanks to a GSoC 2025 project. This is by no means a trivial change so a long tail of issues might occur, please report them if you have found any!

Furthermore, rustup now officially supports the following host platforms:

sparcv9-sun-solaris
x86_64-pc-solaris

Also, rustup will start automatically inserting the right $PATH entries during rustup-init for the following shells, in addition to those already supported:

tcsh
xonsh

This release also comes with other quality-of-life improvements, to name a few:

When running rust-analyzer via a proxy, rustup will consider the rust-analyzer binary from PATH when the rustup-managed one is not found.
- This should be particularly useful if you would like to bring your own rust-analyzer binary, e.g. if you use Neovim, Helix, etc. or are developing rust-analyzer itself.
Empty environment variables are now treated as unset. This should help with resetting configuration values to default when an override is present.
rustup check will use different exit codes based on whether new updates have been found: it will exit with 100 on any updates or 0 for no updates.

Furthermore, @FranciscoTGouveia has joined the team. 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 and are actively looking forward to what we can achieve together.

Further details are available in the changelog!

How to update

If you have a previous version of rustup installed, getting the new one is as easy as stopping any programs which may be using rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

If you don't have it already, you can get rustup from the appropriate page on our website.

Rustup's documentation is also available in the rustup book.

Caveats

Rustup releases can come with problems not caused by rustup itself but just due to having a new release.

In particular, anti-malware scanners might block rustup or stop it from creating or copying files, especially when installing rust-docs which contains many small files.

Issues like this should be automatically resolved in a few weeks when the anti-malware scanners are updated to be aware of the new rustup release.

Thanks

Thanks again to all the contributors who made this rustup release possible!

Rustup 1.29.0 beta: Call for Testing!

2025-12-20T00:00:00+00:00

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

What's new

As usual, we would be happy to receive regression/breakage reports of any kind, especially regarding the installation and/or usage on the following environments:

New host platforms:
- sparcv9-sun-solaris pr#4380
- x86_64-pc-solaris pr#4380
New shells:
- tcsh pr#4459
- xonsh pr#4626
Environments where you would like to bring your own rust-analyzer binary (such as r-a developers and certain Neovim/Helix users): rustup will now consider the rust-analyzer binary from PATH when the rustup-managed one is not found. pr#4324

Environments where you would like to override an environment variable back to the default: rustup now treats empty values as unset. pr#4422

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.

Finally, please don't forget to check out the corresponding section in our CHANGELOG.md for the complete list of changes included in this version.

Acknowledgements

A big thank you to:

@djc for continuously polishing the codebase to get rid of a whole lot of historical burden and carefully shaping the final form of preliminary concurrency support we have today;
@ChrisDenton for the careful handling of IO and Windows-related complexities;
@FranciscoTGouveia for joining me in the GSoC event to investigate the possibilities and lay the foundation of concurrency in rustup;
@Kobzol for enabling and organizing rustup's participation in GSoC 2025 and improving our CLI's cold start performance;
... and many other contributors who have made this new release possible!

Many thanks for everyone's continued support! Wishing you a magical holiday season surrounded by love, peace, and laughter 🍀

Announcing rustup 1.28.2

2025-05-05T00:00:00+00:00

The rustup team is happy to announce the release of rustup version 1.28.2. Rustup is the recommended tool to install Rust, a programming language that empowers everyone to build reliable and efficient software.

What's new in rustup 1.28.2

The headlines of this release are:

The cURL download backend and the native-tls TLS backend are now officially deprecated and a warning will start to show up when they are used. pr#4277
- While rustup predates reqwest and rustls, the rustup team has long wanted to standardize on an HTTP + TLS stack with more components in Rust, which should increase security, potentially improve performance, and simplify maintenance of the project. With the default download backend already switched to reqwest since 2019, the team thinks it is time to focus maintenance on the default stack powered by these two libraries.
- For people who have set RUSTUP_USE_CURL=1 or RUSTUP_USE_RUSTLS=0 in their environment to work around issues with rustup, please try to unset these after upgrading to 1.28.2 and file an issue if you still encounter problems.
The version of rustup can be pinned when installing via rustup-init.sh, and rustup self update can be used to upgrade/downgrade rustup 1.28.2+ to a given version. To do so, set the RUSTUP_VERSION environment variable to the desired version (for example 1.28.2). pr#4259
rustup set auto-install disable can now be used to disable automatic installation of the toolchain. This is similar to the RUSTUP_AUTO_INSTALL environment variable introduced in 1.28.1 but with a lower priority. pr#4254
Fixed a bug in Nushell integration that might generate invalid commands in the shell configuration. Reinstalling rustup might be required for the fix to work. pr#4265

How to update

If you have a previous version of rustup installed, getting the new one is as easy as stopping any programs which may be using rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

If you don't have it already, you can get rustup from the appropriate page on our website.

Rustup's documentation is also available in the rustup book.

Caveats

Rustup releases can come with problems not caused by rustup itself but just due to having a new release.

In particular, anti-malware scanners might block rustup or stop it from creating or copying files, especially when installing rust-docs which contains many small files.

Issues like this should be automatically resolved in a few weeks when the anti-malware scanners are updated to be aware of the new rustup release.

Thanks

Thanks again to all the contributors who made this rustup release possible!

Announcing rustup 1.28.1

2025-03-04T00:00:00+00:00

The rustup team is happy to announce the release of rustup version 1.28.1. Rustup is the recommended tool to install Rust, a programming language that is empowering everyone to build reliable and efficient software.

Challenges with rustup 1.28.0

rustup 1.28.0 was a significant release with many changes, and there was a quick response from many folks that this release broke their processes. While we considered yanking the release, we worried that this would cause problems for people who had already updated to adopt some of the changes. Instead, we are rolling forward with 1.28.1 today and potentially further bugfix releases to address the feedback that comes in.

We value all constructive feedback -- please keep it coming in the issue tracker. In particular, the change with regard to implicit toolchain installation is being discussed in this issue.

What's new in rustup 1.28.1

This release contains the following fixes:

Automatic install is enabled by default but can be opted out by setting RUSTUP_AUTO_INSTALL environment variable to 0. pr#4214 pr#4227
rustup show active-toolchain will only print a single line, as it did in 1.27. pr#4221
Fixed a bug in the reqwest backend that would erroneously timeout downloads after 30s. pr#4218
Use relative symlinks for proxies. pr#4226

How to update

If you have a previous version of rustup installed, getting rustup 1.28.1 is as easy as stopping any programs which may be using Rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

If you don't have it already, you can get rustup from the appropriate page on our website.

Rustup's documentation is also available in the rustup book.

Caveats

Rustup releases can come with problems not caused by rustup itself but just due to having a new release. As such, we recommend paying attention to the following potential issues in particular:

Anti-malware scanners might be blocking rustup or stopping it from creating or copying files (especially when installing rust-docs, since it contains many small files).
In your CI environment, rustup might fail when trying to perform a self-update.

This is a known issue, and in the case where this issue does occur, we recommend applying the following workaround at the beginning of your workflow:
```
$ rustup set auto-self-update disable
```
Also, starting from 1.28.0, rustup will no longer attempt to self-update in CI environments, so this workaround should not be necessary in the future.

These issues should be automatically resolved in a few weeks when the anti-malware scanners are updated to be aware of the new rustup release, and the hosted version is updated across all CI runners.

Thanks

Thanks to the rustup and t-release team members who came together to quickly address these issues.

Announcing Rustup 1.28.0

2025-03-02T00:00:00+00:00

The rustup team is happy to announce the release of rustup version 1.28.0. Rustup is the recommended tool to install Rust, a programming language that is empowering everyone to build reliable and efficient software.

What's new in rustup 1.28.0

This new release of rustup has been a long time in the making and comes with substantial changes.

Before digging into the details, it is worth mentioning that Chris Denton has joined the team. Chris has a lot of experience contributing to Windows-related parts of the Rust Project -- expertise we were previously lacking -- so we're happy to have him on board to help address Windows-specific issues.

The following improvements might require changes to how you use rustup:

rustup will no longer automatically install the active toolchain if it is not installed.
- To ensure its installation, run rustup toolchain install with no arguments.
- The following command installs the active toolchain both before and after this change:
```
rustup show active-toolchain || rustup toolchain install
# Or, on older versions of PowerShell:
rustup show active-toolchain; if ($LASTEXITCODE -ne 0) { rustup toolchain install }
```
Installing a host-incompatible toolchain via rustup toolchain install or rustup default will now be rejected unless you explicitly add the --force-non-host flag.

Rustup now officially supports the following host platforms:

aarch64-pc-windows-msvc
loongarch64-unknown-linux-musl

This release also comes with various quality-of-life improvements, to name a few:

rustup show's output format has been cleaned up, making it easier to find out about your toolchains' status.
rustup doc now accepts a flag and a topic at the same time, enabling quick navigation to specific parts of more books.
rustup's remove subcommands now support more aliases such as rm and del.
Basic support for nushell has been added.

We have additionally made the following internal changes:

The default download backend has been changed from reqwest with native-tls to reqwest with rustls.
- RUSTUP_USE_CURL and RUSTUP_USE_RUSTLS can still be used to change the download backend if the new backend causes issues. If issues do happen, please let us know.
- The default backend now uses rustls-platform-verifier to verify server certificates, taking advantage of the platform's certificate store on platforms that support it.
When creating proxy links, rustup will now try symlinks first and fall back to hardlinks, as opposed to trying hardlinks first.
A new RUSTUP_LOG environment variable can be used to control tracing-based logging in rustup binaries. See the dev guide for more details.

Finally, there are some notable changes to our official website as well:

The overall design of the website has been updated to better align with the Rust Project's branding.
It is now possible to download the prebuilt rustup-init.sh installer for the aarch64-pc-windows-msvc host platform via https://win.rustup.rs/aarch64.

Further details are available in the changelog!

How to update

If you have a previous version of rustup installed, getting rustup 1.28.0 is as easy as stopping any programs which may be using Rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

If you don't have it already, you can get rustup from the appropriate page on our website.

Rustup's documentation is also available in the rustup book.

Caveats

Rustup releases can come with problems not caused by rustup itself but just due to having a new release. As such, we recommend paying attention to the following potential issues in particular:

Anti-malware scanners might be blocking rustup or stopping it from creating or copying files (especially when installing rust-docs, since it contains many small files).
In your CI environment, rustup might fail when trying to perform a self-update.

This is a known issue, and in the case where this issue does occur, we recommend applying the following workaround at the beginning of your workflow:
```
$ rustup set auto-self-update disable
```
Also, starting from 1.28.0, rustup will no longer attempt to self-update in CI environments, so this workaround should not be necessary in the future.

These issues should be automatically resolved in a few weeks when the anti-malware scanners are updated to be aware of the new rustup release, and the hosted version is updated across all CI runners.

Thanks

Thanks again to all the contributors who made rustup 1.28.0 possible!

Announcing Rustup 1.27.1

2024-05-06T00:00:00+00:00

The Rustup team is happy to announce the release of Rustup version 1.27.1. Rustup is the recommended tool to install Rust, a programming language that is empowering everyone to build reliable and efficient software.

If you have a previous version of Rustup installed, getting Rustup 1.27.1 is as easy as stopping any programs which may be using Rustup (e.g. closing your IDE) and running:

$ rustup self update

Rustup will also automatically update itself at the end of a normal toolchain update:

$ rustup update

If you don't have it already, you can get Rustup from the appropriate page on our website.

What's new in Rustup 1.27.1

This new Rustup release involves some minor bug fixes.

The headlines for this release are:

Prebuilt Rustup binaries should be working on older macOS versions again.
rustup-init will no longer fail when fish is installed but ~/.config/fish/conf.d hasn't been created.
Regressions regarding symlinked RUSTUP_HOME/(toolchains|downloads|tmp) have been addressed.

Full details are available in the changelog!

Rustup's documentation is also available in the Rustup Book.

Thanks

Thanks again to all the contributors who made Rustup 1.27.1 possible!

Anas (0x61nas)
cuiyourong (cuiyourong)
Dirkjan Ochtman (djc)
Eric Huss (ehuss)
eth3lbert (eth3lbert)
hev (heiher)
klensy (klensy)
Chih Wang (ongchi)
Adam (pie-flavor)
rami3l (rami3l)
Robert (rben01)
Robert Collins (rbtcollins)
Sun Bin (shandongbinzhou)
Samuel Moelius (smoelius)
vpochapuis (vpochapuis)
Renovate Bot (renovate)