The Rust Release Team announced Rust 1.100.0, the latest version of the Rust programming language, in a post on the official Rust Blog dated November 12, 2026. The never type (!), long confined to experimental status, is now usable on stable Rust, and the core of the Allocator API, which lets developers swap out how memory is allocated, has been stabilized as well. Cargo, the package manager, also gains a setting that keeps recently published versions out of dependency updates.

The never type reaches stable after about 10 years

The official blog presents the stabilization as the result of "10 years and 5 failed stabilization attempts." The never type represents computations that never produce a value. Starting with this release, ! can be written anywhere a type is allowed, so code such as Result<T, !> can express in the type system that an error cannot occur. The standard library's Infallible is now an alias for !.

The change also carries a compatibility impact. In editions before 2024 (2015, 2018 and 2021), never-type fallback changes from () to !. The blog says the change will go unnoticed in most cases, but notes that the compiler may now flag more code as unreachable. According to the team, future-compatibility warnings about this change were issued in advance.

The core Allocator API, DropGuard and other new building blocks

The core parts of allocator_api are now stable, allowing the Allocator trait to be used with Vec and Box. Functions such as Vec::new_in and Box::new_in have joined the stable API. The Rust project describes this as the foundation of its "Allocators 1.0" goal and plans to extend support to other collections and pointer types.

A new type, core::mem::DropGuard, has also landed. It runs a specified closure when the value is dropped and implements Deref and DerefMut. The associated function dismiss returns the inner value without running the closure. It is a building block for writing code that rolls back state when an operation fails.

The new unsafe function std::mem::conjure_zst is now the recommended way to create a value of a zero-sized type. Many other APIs were stabilized as well, including Vec::from_fn, bool::toggle, Box::map, Arc::map and str::trim_prefix.

Cargo revisits how it handles dependencies and caches

Cargo now warns about unused dependencies by default. The lint is named cargo::unused_dependencies and can be configured in the new [lints.cargo] table in Cargo.toml. It only fires when every build target that could use the dependency is built, so it does not appear when building only part of a project, as with cargo check --bin foo. Unused dev-dependencies are not reported either.

The other headline feature is a cooldown setting called min-publish-age. Adding a line such as global-min-publish-age = "3 days" under [registry] in .cargo/config.toml makes Cargo skip versions published more recently than that when updating. Individual updates can be exempted with an environment variable. The official blog points out that versions without publish-time information in the index are never held back and that cargo install ignores the setting, cautioning that cooldowns alone are not a complete defense.

Build caching has changed too. The build-dir now applies the build-configuration hash consistently, and artifacts are organized by build step rather than by file type. The aim is to reduce cache collisions, but the team says build processes that relied on workarounds may break.

Developers should check existing projects after updating

Users who installed Rust through rustup can update to 1.100.0 with rustup update stable. The never-type fallback change and the new Cargo cache layout can affect build results in existing projects. After updating, it is worth checking whether CI produces new warnings or whether steps that depend on the old cache layout fail.

Supply-chain protection moves closer to a standard feature of the official tools

This section is our own view. The most notable change in this release is the official adoption of min-publish-age. Attacks that slip a malicious package version in right after publication have repeatedly been a problem for package managers in other languages as well. Waiting just a few days can avoid the damage in some cases, so having the setting built into the official tool matters. Still, as the official blog itself makes clear, it is not a complete defense, and it is best used alongside existing measures such as dependency audits.

Summary

Rust 1.100.0 closes the book on two long-standing efforts: the never type and the Allocator API. Cargo gains warnings for unused dependencies and a cooldown that delays the adoption of new versions. Because the release includes compatibility-related changes, developers should read the explanations on the official blog before updating.