rustup 1.29.1: Fix Your CI Before 1.30 Breaks It

rustup 1.29.1 landed on September 1 with three meaningful changes: parallel update checks, a local HTTP server for offline docs, and the deprecation warnings that should have shipped in 1.28.0 instead of a cold removal. If your CI uses rustup show to trigger toolchain installs, it will now print a warning. rustup 1.30 will remove that behavior entirely. You have time — use it.

The Deprecation Warning Is the Story

In March 2025, rustup 1.28.0 removed implicit toolchain installation with no warning period and no opt-out. Scripts broke. CI pipelines failed. The team released a patch (1.28.1) within 24 hours, restored the behavior, and apologized. That incident is what makes 1.29.1’s approach so deliberate.

Implicit installation is the behavior where running something like rustup show in a project directory with a rust-toolchain.toml file would silently install the specified toolchain if it wasn’t present. Convenient, but opaque — especially in CI, where invisible side effects are footguns.

Starting with 1.29.1, triggering implicit installation now prints:

warning: implicit toolchain installation is deprecated
use `rustup install <toolchain>` instead

The fix is straightforward. In your CI configuration, replace any implicit trigger with an explicit install:

# Old (now deprecated — will break in 1.30):
rustup show

# New (explicit, correct):
rustup install stable
# or pin to a specific version:
rustup install 1.80.0

If you want to audit your environment now and opt in to the 1.30 behavior immediately, set the environment variable:

export RUSTUP_AUTO_INSTALL=0
# or via rustup config:
rustup set auto-install disable

Note that cargo and rustc proxy invocations retain implicit install for now — those are not deprecated yet. It’s the direct rustup subcommands that are changing. The full list of RUSTUP environment variables is documented in the official rustup book.

rustup doc –serve: Years in the Making

The --serve flag on rustup doc has been requested for years. The problem: rustup doc opens standard library docs via file:// URLs, which browsers inside Docker containers, WSL2 environments, and other sandboxed setups routinely block. You’d get the docs downloaded locally but couldn’t actually read them.

The fix is one flag:

rustup doc --serve

This starts a local HTTP server bound to 127.0.0.1 serving your local Rust docs. Open the printed URL in your browser — it works in any environment that can reach localhost. The server rejects path traversal attempts and never binds to external interfaces, so there’s no security concern running it in a dev environment.

If you’re doing Rust development inside devcontainers or on a remote machine via VS Code Remote, this is the change you’ve been waiting for. Port-forward the address and you have offline Rust docs in any browser.

Parallel Installs (Finally)

rustup update previously checked each installed toolchain serially. With 1.29.1, update checks happen in parallel — if you have stable, nightly, and a pinned version installed, it now checks all three simultaneously rather than waiting on each in sequence.

The same applies to rustup component add with multiple arguments:

rustup component add rust-src rust-analyzer clippy rustfmt

All four components now install concurrently. For large initial setups or CI environments that install fresh toolchains on every run, this adds up.

Windows: ARM64 and a Footgun Fix

Two Windows-specific changes worth noting. First, aarch64-pc-windows-gnullvm is now a supported host toolchain — native Rust compilation on ARM64 Windows (Copilot+ PCs) via the GNU/LLVM backend, without needing the MSVC toolchain.

Second, installing an i686-pc-windows-* host toolchain (32-bit) on a 64-bit Windows machine now requires --force-non-host. This prevents accidentally setting your host toolchain to 32-bit when you almost certainly want 64-bit. Cross-compiling to i686 as a target is unaffected.

Upgrading

Check your current version and update with:

rustup --version
rustup self update

Running rustup update also updates rustup itself alongside your toolchains. The full rustup 1.29.1 release announcement on the Rust blog has the complete changelog.

The Takeaway

The --serve flag is the quiet win — a long-requested fix for a real pain point that most coverage won’t lead with. But the deprecation warning is the urgent one. The rustup team burned trust with 1.28.0 and earned it back with 1.28.1’s rapid restoration; 1.29.1 shows they’re following through with a proper migration path. If your CI pipeline relies on implicit installation, the warning is running now. Fix it before 1.30 makes it your incident.