Provenance Record

News, 935 words, 121-character title. Clear structure: Overview, never type, Allocator API, library additions, Cargo, compatibility and platform notes, What We Don't Know. Quotes are verbatim and attributed to the Rust Blog or the GitHub release notes; the Herald's own counts and conversions are labelled as such.

Read all six snapshots (source-0..5.html.gz in sources/2026-11/rust-11000-stabilizes-the-never-type-and-core-parts-of-the-allocator-api-and-adds-opt-in-dependency-cooldowns-to-cargo/); manifest suspicious_patterns null for all six. source-0 Rust Blog (Nov. 12, 2026, The Rust Release Team): confirms 'After 10 years and 5 failed stabilization attempts, the never type is finally stable!', 'this release allows naming the never type anywhere' with Result<T, !>, Infallible aliased to the never type, 'This release changes the "never type fallback" from () to ! in editions before 2024 (i.e. 2015, 2018, and 2021)', 'should largely be unnoticeable, but can affect code in some rare cases', 'might also make the compiler detect more code as unreachable', 'future compatibility warnings far in advance'; 'the stabilization of the core parts of allocator_api ... currently Vec and Box ... newly-stabilized Allocator trait', Allocators 1.0 project goal; DropGuard and dismiss; conjure_zst (unsafe); three Cargo sections (unused dependencies with cargo::unused_dependencies warn by default and no warning for dev-dependencies, cache collisions/build-dir, min-publish-age 'a.k.a. dependency cooldowns' opt-in via [registry] global-min-publish-age = "3 days", pubtime caveat, 'cargo install ignores the minimum publish age', 'not a complete defense on their own'). The Rust Blog itself uses the term 'dependency cooldowns', so the headline term is the project's, not only the Herald's or the press's. source-1 GitHub release notes: Language 'Stabilize never type'; Libraries 'Stabilize custom allocators'; Platform Support lists only i686-pc-windows-gnu ('now a tier 2 without host tools target', PR 161681), wasm32-wasip3 to Tier 2 and Tier 3 powerpc64-sony-ps3 (the article's description is complete); Cargo bullets: lint system and cargo::unused_dependencies (#17298), minimum publish age 'also known as dependency cooldowns' with 'unless they are already in Cargo.lock' (RFC 3923, #17335), cargo install lockfile (#17388), new build directory layout 'not a stable interface' (#17354); Compatibility Notes: I recounted 20 entries (Closures/if let; dyn-compatibility; Infallible alias; never type fallback on all editions; box patterns; query cycle errors; grapheme extenders; let-else; Iterator min/max; SSE/AVX softfloat; Xtensa windowed; windows-gnullvm; ARMv7-A d32; x86 Rust ABI SSE; ambiguous_glob_imported_traits; cortex-a53-835769; Box impls generalised to arbitrary allocators; Unicode 18.0.0; WASI SDK 33 to 34; ARM target-feature hard errors) = 20, matching the article's 'the Herald's count'. Release timestamp: GitHub API published_at 2026-11-12T18:19:42Z (tag 1.100.0), matching the page's '12 Nov 18:19' and the article's '18:19 UTC'; the Cargo changelog (doc.rust-lang.org/nightly/cargo/CHANGELOG.html, not cited) lists 'Cargo 1.100 (2026-11-12)' and attributes the lint system, min-publish-age, build-dir layout and cargo install lockfile change to 1.100, so all Cargo changes are attributed to the right release. source-2 Phoronix, read via the Archive.org capture (web.archive.org/web/20261112190158/..., sha256 of decompressed snapshot 2b7247a9...; the live page returned 200 but the script stored the archive copy): byline 'Written by Michael Larabel ... on 12 November 2026 at 01:51 PM EST' (= 18:51 UTC, the Herald's conversion), covers the release itself: never type stable, 'stabilizes core parts of Rust's Allocator API', unused dependencies, min-publish-age as dependency cooldown. source-3 LWN 'Rust 1.100.0 released' (jzb): page shows only 'Posted November 12, 2026'; the LWN RSS feed (lwn.net/headlines/rss, fetched live with a browser User-Agent) gives pubDate Thu, 12 Nov 2026 19:09:19 +0000, matching '19:09 UTC according to its feed'; covers never type, 'core parts of the Allocator API', unused dependencies. source-4 Linuxiac (Bobby Borisov): page meta article:published_time / datePublished 2026-11-12T23:45:19+00:00 (matches '23:45 UTC'); covers the release itself, Result<T, !> example, 'should affect few projects, but some existing code or dependencies may require updates' (verbatim), core Allocator API, cooldown optional and not applying to cargo install. Nothing is attributed to an outlet that does not say it; the claim 'All three report the never type stabilization and the stabilization of the core Allocator API' holds for each. source-5 rust-lang/rust PR #162288 'Drop host tools from i686-pc-windows-msvc' (mati865): merged, '1.100.0 milestone' added Sep 9, 2026; GitHub API: merged_at 2026-09-09T20:04:25Z, milestone 1.100.0, merge commit 32ffad32; compare 32ffad3...1.100.0 returns status 'ahead' with merge_base = 32ffad32, i.e. the merge commit is an ancestor of the 1.100.0 tag. The page also carries cross-referenced downstream commit messages (smol-rs/polling, Sep 18) stating 'Rust 1.100 dropped host tools for both i686-pc-windows-msvc (RFC 3999, rust-lang/rust#162288) and i686-pc-windows-gnu'; these are a downstream project's statements, not Rust project statements, but they make the article's closing sentence 'The cited sources do not state in so many words whether the i686-pc-windows-msvc host-tool removal is in the 1.100.0 toolchains' incomplete: clarification filed. Platform-support disagreement: the article reports both facts (the earlier Briefing's both-targets statement; the release notes listing only gnu; PR 162288 merged with the 1.100.0 milestone) without resolving them, as required. It does not repeat either statement flagged by the 2026-09 never-type article's corrections record (428-file diff stat; 'Google engineer'); the September article is described only as having reported the merge with 1.100.0 as its milestone, which matches it. The October Briefing is described accurately (Rust Blog announced host-tool removal for both targets with 1.100.0). Internal links /article/2026-09/11-rust-stabilizes-the-never-type-after-10-years-and-five-failed-attempts, /article/2026-10/06-rust-demotes-32-bit-windows-targets-... and /article/2026-10/24-dependency-cooldowns-spread-from-pnpm-... all exist as published articles and are described correctly. Sources: 6 (News minimum 3); independent outlets: Phoronix, LWN, Linuxiac = 3 (LWN's item is a short pointer to the blog post). Allowlist: all hosts (blog.rust-lang.org, github.com, phoronix.com, lwn.net, linuxiac.com) already allowlisted; no additions. Anthropic disclosure: not required - the story is the Rust 1.100.0 release; Anthropic, Claude and Bun appear nowhere in the headline, summary, lead or body (the only occurrences are 'Assisted-by: Claude' lines in downstream commit messages in the PR 162288 page, which the article does not report). Rule 15 not applicable.

Headline, summary and lead hold: 'Stabilizes the Never Type' (the ! type, now nameable anywhere, with Infallible aliased and pre-2024 fallback changed from () to !; release notes 'Stabilize never type'); 'Core Parts of the Allocator API' matches the Rust Blog, Phoronix and LWN scope (Allocator trait, Global, System, new_in/with_capacity_in etc. on Box and Vec; Rust Blog says more collections remain); 'Opt-In Dependency Cooldowns' is Cargo's minimum publish age (registry.global-min-publish-age), opt-in, stabilized in 1.100 per the blog, release notes and Cargo changelog. Release date November 12, 2026 with the stated basis (blog date without time zone; GitHub release 18:19 UTC) verified. Claim-accuracy tests run: quantifiers ('both', 'all three', 'each stamped after') hold item by item (Phoronix 18:51, LWN 19:09, Linuxiac 23:45 UTC are all after 18:19 UTC); 'three Cargo changes' matches the three Cargo sections of the blog; 'Among others' qualifiers used on the library list; the Compatibility Notes count of 20 recomputed and labelled the Herald's; the EST-to-UTC conversion labelled the Herald's. One incomplete absence statement (see clarification). No other wrong or unsourced specifics found.

Accurate, well-sourced release News with correctly labelled Herald counts and conversions; approved with one clarification on an incomplete absence claim in the closing section. Featured candidacy: 2 - the never type landing after ten years and the first stable Allocator API are significant for the broad Rust developer audience.