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-07-27
stories 152

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

MIRI SUBTREE LANDS ALONGSIDE UNSAFE EII ENFORCEMENT IN COMPILER

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

The Rust compiler just got stricter about unsafe trait implementations, while the core interpreter received a major update across 105 commits.

Miri's subtree update [1] syncs the interpreter to the latest from the miri repository, bringing improved undefined behavior detection to the compiler. The same cycle enforces a critical safety rule: unsafe explicit implementations of implemented traits (EIIs) on safe traits are now rejected, matching the behavior of unsafe impl on safe trait declarations [2]. This closes a soundness gap that let unsound code slip through diagnostics. In parallel, the compiler improved attribute error messages [3] by simplifying suggestion logic after recent span tracking work [3], and cleaned up a redundant paren-sugar feature gate that was already covered by rustc_attrs [4]. On the tooling side, rust-analyzer shipped version 2026-07-27 [5] with support for inactive-code diagnostics inside macros [6], while also removing compatibility code for old Rust versions no longer in support [7]. The crates.io index saw routine creations and updates across zerocli [8], solray [9], runifold-provider-openai [10], aetherion-cli [11], and promptbridge [12]. Docs.rs refreshed dependencies including base64 0.23 [13] and improved documentation clarity around limited feature metadata support [14].

Action items

References

  1. [1] miri subtree update ↗ rust-lang/rust
  2. [2] Check unsafe impls on safe EIIs ↗ rust-lang/rust
  3. [3] Improve workings of attribute suggestions ↗ rust-lang/rust
  4. [4] Rollup merge of #159826 - mejrs:sugar_parens, r=JonathanBrouwer rust-lang/rust ↗
  5. [5] 2026-07-27 ↗ rust-lang/rust-analyzer
  6. [6] feat: Support inactive-code diagnostic in macros ↗ rust-lang/rust-analyzer
  7. [7] internal: Cleanup code for old Rust versions ↗ rust-lang/rust-analyzer
  8. [8] Create crate `zerocli` rust-lang/crates.io-index ↗
  9. [9] Update crate `solray` rust-lang/crates.io-index ↗
  10. [10] Create crate `runifold-provider-openai` rust-lang/crates.io-index ↗
  11. [11] Create crate `aetherion-cli` rust-lang/crates.io-index ↗
  12. [12] Update crate `promptbridge` rust-lang/crates.io-index ↗
  13. [13] chore(deps): update rust crate base64 to 0.23 ↗ rust-lang/docs.rs
  14. [14] Make infobox about limited feature metadata clearer ↗ rust-lang/docs.rs

Quick answers

What shipped in Rust on July 27, 2026?
The Rust compiler just got stricter about unsafe trait implementations, while the core interpreter received a major update across 105 commits. In total, 105 commits, 45 pull requests, and 2 releases landed.
Who contributed to Rust on July 27, 2026?
11 developers shipped this update, including bors, RalfJung, mejrs, nnethercote, Jonathan Brouwer, AsakuraMizu, renovate, and Mikolaj Wielgus, and 3 more.
What were the notable Rust updates?
miri subtree update, Check unsafe impls on safe EIIs, and Improve workings of attribute suggestions.