RepoJournal
Rust

@rust-lang

The Rust language, Cargo, and the standard library

Pick a date

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

The Wire · Showcase

RUSTDOC ICE FIX AND SOLVER UPGRADES SHIP OVERNIGHT

By RepoJournal · Filed · About Rust

Rustdoc crashed on deprecated notes in re-export chains. That's fixed [ref:15]. Two major rollups just landed with eager param_env normalization and core::io changes that reshape standard library architecture.

The first critical fix lands in rustdoc [1], which was throwing internal compiler errors when deprecated notes appeared on inlined re-export chains. The fix resolves those links from the owning re-export instead, with regression tests in place [2]. On the solver front, two rollups shipped back-to-back. The first enables eager param_env normalization in the new solver [3], a foundational change for type inference. The second rollup [4] adds the `-Zforce-intrinsic-fallback` flag for intrinsic handling, moves `std::io::Seek` into `core::io` to decouple standard library dependencies, and introduces `WriteThroughCursor` to the cursor API. Miri caught upstream changes and pulled them in [5], while the locals handling for Priroda debug-info is now merged [6], improving visibility into projected debug-info places in the locals command. Five crate index updates crossed the wire overnight [7][8][9][10][11], all routine maintenance.

Action items

References

  1. [1] Fix rustdoc ICE on deprecated note in inlined re-export chain rust-lang/rust
  2. [2] Rollup merge of #158820 - TaKO8Ki:fix-deprecated-note-reexport-chain, r=GuillaumeGomez rust-lang/rust
  3. [3] Auto merge of #158864 - JonathanBrouwer:rollup-re2xAGf, r=JonathanBrouwer rust-lang/rust
  4. [4] Auto merge of #158847 - jhpratt:rollup-MkjhKjV, r=jhpratt rust-lang/rust
  5. [5] Automatic Rustup ↗ rust-lang/miri
  6. [6] [Priroda] Handle projected debug-info locals ↗ rust-lang/miri
  7. [7] Update crate `greentic-bundle-reader` rust-lang/crates.io-index
  8. [8] Update crate `nirs4all-io` rust-lang/crates.io-index
  9. [9] Update crate `cards2pack-core` rust-lang/crates.io-index
  10. [10] Update crate `bundle-standard-core` rust-lang/crates.io-index
  11. [11] Update crate `nirs4all-io-core` rust-lang/crates.io-index

FAQ

What changed in Rust on July 7, 2026?
Rustdoc crashed on deprecated notes in re-export chains. That's fixed . Two major rollups just landed with eager param_env normalization and core::io changes that reshape standard library architecture.
What should Rust teams do about it?
Test your rustdoc builds if you use deprecated notes on re-exports • Review eager param_env normalization impact on your type inference patterns • Update miri and sync with latest rustc if you run bleeding-edge tooling
Which Rust repositories shipped on July 7, 2026?
rust-lang/rust, rust-lang/miri, rust-lang/crates.io-index

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.