Rust 1.100.0 ships, and its own version number breaks CI checks
Rust 1.100.0 stabilises the never type and custom allocators, but the first three-digit minor version trips up any script that compares versions as text or as a decimal.
Rust 1.100.0 became stable today, 12 November, the first release with a three-digit minor version. The official release notes list the never type as stable after ten years and five earlier stabilisation attempts, alongside a stable Allocator API for custom allocators on Vec, Box, Rc and Arc, a new Cargo lint system, and “minimum publish age” cooldowns that can stop Cargo resolving a crate version published too recently.
The version number itself is the practical catch. Rust’s own notes warn that a script comparing the version as plain text or as a decimal number reads 1.100 as older than 1.99, because "1.1" sorts before "1.9" as a string, and 1.100 parses as the decimal 1.1. Any shell script, Makefile or CI gate written that way now reports “Rust too old” and fails, even on the newest compiler.
Why it matters: if your build pipeline checks a minimum Rust version with a naive string or decimal comparison, it broke today without you changing anything. The fix is to compare each version segment as a whole number, not the version as one string.
# breaks: "1.100" reads as older than "1.99"
[ "$(rustc --version | awk '{print $2}')" \< "1.99" ] && echo "too old"
# works: compares each part as an integer
printf '%s\n%s\n' "1.100.0" "1.99.0" | sort -V | tail -1