$ cat rust-lang/week/2026-10-05.log
the week in review · Oct 5 – Oct 11, 2026
cc-rs 1.7.0 ships, Cargo stabilizes trim-paths
By RepoJournal · composed from the cited sources · human-reviewed weekly · methodology
Miri's 19-PR rollup fixed a repr(C) ZST ABI bug, and rustc made the new semicolon lint stop reporting in dependencies.
cc-v1.7.0 rust-lang/cc-rs
The build-script helper gains `Tool::get_envs` and now stores tool env as `Arc<OsStr>` pairs, with `Tool::env` deprecated in favor of it. It also links `c++` when Clang uses libc++ and adds `CC_MASM_ASM`, falling back to `llvm-ml` for MASM. If your build scripts pin cc, the deprecation is the item to plan around.
feat(trim-paths): stabilize `profile.trim-paths` rust-lang/cargo
Path trimming for release artifacts is now a stable profile option, resolving the long-standing Cargo and rustc issues behind the trim-paths RFC. Debug and source paths stop leaking into shipped binaries once you set it.
ops: Resolve `unpinned-uses` and `ref-version-mismatch` rust-lang/josh-sync
In pursuit of getting more `zizmor` lints enforced across `rust-lang` repos through `crabwatch`, this change fixes all findings of the `unpinned-uses` and `ref-version-mismatch` rules. Worth reading as a template if you maintain workflows in the org.
fix(pkgid): avoid panic on malformed protocol URLs (#17548) rust-lang/cargo
`strip_url_protocol()` now returns a `Result` instead of unwrapping, so the git, registry, and path callers propagate the error and malformed protocol URLs produce a normal cargo diagnostic rather than a panic.
even more `tests/crashes` migration for `-Znext-solver` rust-lang/rust
Test migration for the next trait solver continues across the compiler tree, with the linked issue list still tracking failures blocked on the trait-system refactor. Momentum for the new solver, noise for anyone bisecting nightly compiler behavior.
Rollup merge of #163364 - RalfJung:semicolon-no-report-in-deps, r=mati865 rust-lang/rust
The new `semicolon_in_expressions_from_non_local_macros` lint was made report-in-deps immediately, without a crater run; the rollup reverts that so it stops firing inside dependencies.
Auto merge of #163754 - JonathanBrouwer:rollup-fdgcPnD, r=JonathanBrouwer rust-lang/rust
The rollup adds a future-compatibility warning for `#[panic_handler]` on `unsafe fn`, plus documentation for the `no_main` and `repr` attributes. As the RFC text puts it, the warning phase precedes the error, so expect breakage in a later release.
$ ls rust-lang/week/ # the briefings behind this review
Keep up with Rust in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.
Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.