RepoJournal
Rust

@rust-lang

The Rust language, Cargo, and the standard library

What actually shipped in Rust, written up every day — commits, pull requests, releases, and security advisories.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Rust Full archive →

The Wire · Showcase

RUST CI OUTAGE POSTMORTEM PUBLISHED, CRATES.IO DATADOG REPORTING GOES LIVE

By RepoJournal · Filed · About Rust

The infra team shipped the 2026-07-02 CI outage postmortem after this week's meeting, while crates.io landed a major shift in monitoring that decouples evaluation from incident reporting.

The rust-lang/rust CI outage that hit on July 2nd now has a full postmortem in the infra-team repo [1], marking the completion of the incident review cycle discussed during the weekly sync. Meanwhile, crates.io's monitoring pipeline got a significant refactor: the `monitor` binary now separates invariant evaluation from provider-specific reporting [3], which means database checks return provider-independent `CheckResult` objects that can route to multiple systems. This architecture change powers the new Datadog service check submissions [2], which is currently disabled by default behind a rollout flag while the team validates the integration. The service check implementation includes full HTTP test coverage for authentication, batched serialization, and response validation [4]. On the stdlib side, error messages for `TryFromIntError` got more granular [5], replacing the generic "out of range" message with specific feedback based on `IntErrorKind`. Miri added support for ARM NEON table intrinsics [7], completing portable_simd's needs, and caught a documentation typo in the RUSTFLAGS target-feature flag [8]. Compiler cleanup continues with removal of dead code from unsafe attrs handling [6] and early-exit closure elimination in the run_compiler path [9].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Add 2026-07-02 rust-lang/rust CI outage postmortem ↗ rust-lang/infra-team
  2. [2] datadog: Submit `monitor` results as service checks ↗ rust-lang/crates.io
  3. [3] monitor: Separate evaluation from PagerDuty reporting rust-lang/crates.io
  4. [4] datadog: Add service check submissions rust-lang/crates.io
  5. [5] Rollup merge of #156225 - sorairolake:improve-try-from-int-error-description, r=dtolnay rust-lang/rust
  6. [6] Rollup merge of #159590 - oli-obk:unsafe_attrs_old, r=petrochenkov rust-lang/rust
  7. [7] support `neon.tbl*` intrinsics ↗ rust-lang/miri
  8. [8] readme: fix misspelling of `-Ctarget-feature` rust-lang/miri
  9. [9] Remove `early_exit` closures rust-lang/rust

Quick answers

What shipped in Rust on July 22, 2026?
The infra team shipped the 2026-07-02 CI outage postmortem after this week's meeting, while crates.io landed a major shift in monitoring that decouples evaluation from incident reporting. In total, 106 commits and 35 pull requests landed.
Who contributed to Rust on July 22, 2026?
12 developers shipped this update, including bors, jieyouxu, Ubiratan Soares, Turbo87, renovate, Nicholas Nethercote, Oli Scherer, and Jonathan Brouwer, and 4 more.
What were the notable Rust updates?
Add 2026-07-02 rust-lang/rust CI outage postmortem, datadog: Submit `monitor` results as service checks, and monitor: Separate evaluation from PagerDuty reporting.

More from @rust-lang

Daily updates, in your inbox

Follow Rust

What actually shipped in Rust, written up every day — commits, pull requests, releases, and security advisories.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?