RepoJournal
Rust

@rust-lang

The Rust language, Cargo, and the standard library

Pick a date

  1. Sat 16 may
  2. Sun 17 may
  3. Mon 18 may
  4. Tue 19 may
  5. Wed 20 may
  6. Thu 21 may
  7. Sat 23 may
  8. Sun 24 may
  9. Mon 25 may
  10. Tue 26 may
  11. Wed 27 may
  12. Thu 28 may
  13. Fri 29 may
  14. Sat 30 may
  15. Sun 31 may
  16. Mon 1 jun
  17. Mon 8 jun
  18. Tue 9 jun
  19. Today 10 jun

The Wire · Showcase

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

By RepoJournal · Filed · About Rust

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

FAQ

What changed 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.
What should Rust teams do about it?
Update http to 1.4.2 if you're using URI builder with wildcard paths • Review crate deletion requirements if you've been blocked on cleanup • Watch for Xtensa stabilization timeline in compiler PRs
Which Rust repositories shipped on June 9, 2026?
rust-lang/rust, rust-lang/crates.io, rust-lang/regex

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.