112 wires and counting

$ follow Rust

Keep up with Rust in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

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.

$ status

wire 2026-06-09
stories 131

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

RUSTC ROLLUP LANDS XTENSA SUPPORT, CRATES.IO FIXES SELF-REFERENCING BLOCKS

By RepoJournal · Filed · About Rust · Composed from the cited sources · methodology

The compiler gained a major new architecture target while the registry fixed a deletion blocker that was trapping maintainers with circular dependencies.

The rust compiler inbox is moving fast. A 13-PR rollup landed overnight [1] that includes Xtensa architecture support for inline assembly, the first real implementation of compile-time function evaluation, and a new proc-macro `_value` API for number literals. These aren't incremental; Xtensa is a significant embedded win, and comptime functions open new doors for const evaluation. On the registry side, crates.io fixed a critical oversight where self-referencing dependencies were blocking crate deletion [2]. Maintainers trying to clean up old versions were getting trapped because the deletion check couldn't distinguish between legitimate reverse dependencies and a crate depending on itself. That's resolved now. The http crate bumped to 1.4.2 [3] with a fix allowing `"*"` as a valid URI path in the builder, a small but necessary correction for HTTP spec compliance. Meanwhile, the regex team landed a significant performance win [4] by avoiding repeated canonicalization of huge IntervalSets on push operations, addressing a real-world bottleneck hit by lalrpop-generated lexers with massive character ranges. Observability work continues at crates.io with new logging conventions [5] and better error interpolation into messages [6], making the backend easier to debug in production.

Action items

References

  1. [1] Auto merge of #157616 - JonathanBrouwer:rollup-TC4GBP2, r=JonathanBrouwer rust-lang/rust ↗
  2. [2] Ignore self-referencing dependencies when checking crate deletion requirements ↗ rust-lang/crates.io
  3. [3] Update Rust crate http to v1.4.2 ↗ rust-lang/crates.io
  4. [4] perf: Avoid re-canonicalizing the entire IntervalSet on push ↗ rust-lang/regex
  5. [5] Add `docs/LOGGING.md` with backend logging conventions ↗ rust-lang/crates.io
  6. [6] Interpolate error values into log messages ↗ rust-lang/crates.io

Quick answers

What shipped in Rust on June 9, 2026?
The compiler gained a major new architecture target while the registry fixed a deletion blocker that was trapping maintainers with circular dependencies. In total, 107 commits and 24 pull requests landed.
Who contributed to Rust on June 9, 2026?
3 developers shipped this update, including Turbo87, renovate[bot], and Marwes.
What were the notable Rust updates?
Auto merge of #157616 - JonathanBrouwer:rollup-TC4GBP2, r=JonathanBrouwer, Ignore self-referencing dependencies when checking crate deletion requirements, and Update Rust crate http to v1.4.2.