$ the-wire · showcase
rust-analyzer picks up a divergent-let fix; four crates move to trusted publishing
By RepoJournal · Filed · About Rust · Composed from the cited sources · methodology
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
9 people shipped this
Kobzol
@Kobzol
2 cited
github-actions[bot]
@github-actions[bot]
1 cited
Shoyu Vanilla
@ShoyuVanilla
1 cited
renovate
@renovate
1 cited
Mark-Simulacrum
@Mark-Simulacrum
1 cited
bors
@bors
workflows-rust-analyzer
@workflows-rust-analyzer
ChayimFriedman2
@ChayimFriedman2
Ubiratan Soares
@ubiratansoares
Rust's tooling day is mostly plumbing: rust-analyzer shipped its weekly release with a type-checking fix for `let ... else`, and the team repo converted four more crates to trusted publishing while docs.rs and simpleinfra took routine dependency and infrastructure updates.
2026-10-12 rust-lang/rust-analyzer
The weekly rust-analyzer build lands as version 2026-10-12, delivered by automation rather than a hand-cut tag. Nothing in the release notes points to a breaking configuration change, so this is a normal Monday pull for editor users.
Merge pull request #23500 from ChayimFriedman2/let-diverge-else rust-lang/rust-analyzer
When the initializer in a `let` diverges, the `else` branch may now be non-diverging as well, matching rustc's behavior in `compiler/rustc_hir_typeck/src/fn_ctxt/checks.rs`. The change closes rust-analyzer issue 23499, where the IDE flagged `let ... else` code that the compiler accepted, and it is already in this week's release.
Switch `getopts` to trusted publishing and rename its default branch to `main` rust-lang/team
Kobzol moved `getopts` to crates.io trusted publishing and renamed its default branch to `main`. The change is in rust-lang/team, but the real risk sits downstream: if you build tooling against the Rust repo, note that the `getopts` GitHub URL's default branch no longer answers to `master`.
Use trusted publishing for `rustc_apfloat` rust-lang/team
`rustc_apfloat`, `rustc-demangle`, and `backtrace-rs` were all switched to trusted publishing, with two of them also moving their default branch to `main`. Every crate published by the Rust project this way drops long-lived crates.io API tokens in favor of short-lived, CI-issued ones, which removes a standing supply-chain credential from the ecosystem.
fix(deps): update rust crate comrak to 0.56.0 rust-lang/docs.rs
docs.rs bumped `comrak` from 0.55.0 to 0.56.0 in its dependency tree. Docs.rs renders your crates' README markdown through that library, so the update is worth noting only if you depend on the exact rendering of a specific construct.
Grant read access to rustup resources to Jakub rust-lang/simpleinfra
The long tail: simpleinfra granted S3 read-only access to rustup resources for Jakub so the new rustup CI can be debugged, with write and release permissions explicitly coming later, and refreshed crater's Terraform; docs.rs moved `zip` to 9.0.0 and pinned mise 2026.10.8; the crates.io index absorbed five routine crate updates.
