RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Pick a date

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

The Wire · Showcase

MAUI GETS INTELLIGENT CI FAILURE TRIAGE, DOTNET REVERTS ASPNETCORE TOOL CRASH

By RepoJournal · Filed · About .NET

MAUI's CI pipeline now auto-classifies test failures with agentic workflows, while the main dotnet repo rolled back an aggregation that broke ILC compilation on Windows.

MAUI shipped three connected CI improvements overnight that turn flaky test diagnosis from manual labor into automated triage [1][2][3]. The `/review tests` command classifies PR failures as likely self-inflicted, unrelated infrastructure issues, or needing human judgment, while `/review rerun` deterministically reruns specific failures without guessing [4]. This cuts through MAUI's notorious test noise and gets PRs unstuck faster. Simultaneously, dotnet/dotnet reverted the ASP.NET Core tool aggregation that shipped yesterday after discovering it locks source files during ILC compilation on Windows, breaking every official and PR build on main [8]. The android team continued their cleanup sprint: dropping dead build gates after inlining android-platform-support [5], removing unused protobuf-net references [6], and axing a misspelled exception class that was never thrown [7]. Orleans landed three separate IMeterFactory migrations to scope instrumentation properly through dependency injection instead of static globals [9][10][11], tightening observability across messaging, journaling, and Azure storage metrics.

Action items

References

  1. [1] Add CI failure scanner gh-aw workflow (#35734) dotnet/maui
  2. [2] Add /review tests failure review workflow ↗ dotnet/maui
  3. [3] Add gh-aw rerun review scanner ↗ dotnet/maui
  4. [4] Add gh-aw rerun review scanner (#35685) dotnet/maui
  5. [5] [build] Drop always-true _HasCommercialFiles / _AndroidFastDeploymentSupported gates (#11576) dotnet/android
  6. [6] [build] Drop unused protobuf-net references from Mono.AndroidTools (#11592) dotnet/android
  7. [7] [Mono.AndroidTools] Remove obsolete misspelled `IncompatibleCpuAbiExceptiopn` (#11597) dotnet/android
  8. [8] Revert "Aggregate ASP.NET Core tool executables (#7020)" ↗ dotnet/dotnet
  9. [9] chore: use IMeterFactory for MessagingProcessingInstruments ↗ dotnet/orleans
  10. [10] chore: use IMeterFactory for JournalingInstruments ↗ dotnet/orleans
  11. [11] chore: use IMeterFactory for AzureBlobJournalStorageInstruments ↗ dotnet/orleans

FAQ

What changed in .NET on June 8, 2026?
MAUI's CI pipeline now auto-classifies test failures with agentic workflows, while the main dotnet repo rolled back an aggregation that broke ILC compilation on Windows.
What should .NET teams do about it?
Monitor main branch Windows CI for stability after aspnetcoretools revert • Test MAUI CI workflows using the `/review tests` and `/review rerun` commands on your next PR • Update Orleans instrumentation integrations to use new IMeterFactory scopes
Which .NET repositories shipped on June 8, 2026?
dotnet/maui, dotnet/android, dotnet/dotnet, dotnet/orleans

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.