Rust 1.92.0 pre-release testing

The 1.92.0 pre-release is ready for testing. The release is scheduled for December 11. Release notes can be found here.

You can try it out locally by running:

RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable

The index is https://dev-static.rust-lang.org/dist/2025-12-08/index.html.

The release team is also thinking about changes to our pre-release process: we'd love your feedback on this GitHub issue.

6 Likes

Tried this with two large projects (one of which builds ~1000 crates across a multitarget build); no issues at all.

2 Likes

Now it complains if you have a function that produces error with Infallible value in Result (think exec or similar call that won't return if succeeds, but will return error if fails. I'm trying to use unwrap() to cause panic

use std::convert::Infallible;

pub fn dummy() -> Result<Infallible, &'static str> {
    Err("nope")
}

pub fn complains() {
    // note: this expression has type `Infallible`, which is uninhabited
    dummy().unwrap();
}

pub fn also_complains() {
    // = note: this `Result` may be an `Err` variant, which should be handled
    dummy();
}

This works, but ugly.

panic!("{:?}", dummy().unwrap_err());

You should probably report a bug on github / check if one was already reported.

That is from:

and fixed in:

but not backported into 1.92.0.

2 Likes

Rust Release Notes :

It seems they added a panic! for last without documenting it, or am I missing it? (count does document the panic! in Iterator: Iterator in std::iter - Rust)

May warrant a quick backport so we don't innundate folks with new warnings.

1 Like

Is the dec 11 release date a hard deadline? It could be delayed for a day or two to make time for this fix to be backported

1 Like

1.0 and 1.2 were released on Fridays; every other release has been on the Thursday fixed by the six week cadence. It's certainly possible, but more likely that we'd get a quick point release imo

3 Likes