This was caused by rust-overlay's selectLatestNightlyWith silently pinning on the last nightly that included an out-of-date component. This won't stop that from happening, but should catch it much sooner.
FU7S4JHV267EBWLMNE3B7EESCDEDLFJ67UMK75C76CSDONRY3OSAC # Prevent rustc from getting too out-of-date;# rust-overlay's selectLatestNightlyWith silently keeps older versions if components/targets are no longer validuse std assert;export def enforce-rust-version [] {let version_info = rustc --version | parse "rustc {version} ({commit} {date})";# Make sure only 1 row of dataassert equal ($version_info | length) 1;assert equal ($version_info.date | length) 1;# Extract the datelet version_date = $version_info.date | first | into datetime;# Return an error if the version is more than one week oldassert greater $version_date ((date now) - 7day) $"This version of Rust was built (ansi red_bold)($version_date | date humanize)(ansi reset)!Check that all specified targets and extensions are valid.(ansi yellow_bold)HINT(ansi reset): replace `selectLatestNightlyWith` with `nightly.latest.default.override` to debug.";}