RepoJournal
.NET

@dotnet

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

Pick a date

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

The Wire · Showcase

ASPNETCORE FIXES BUILD RACE CONDITION WHILE BUMPING CI TOOLING

By RepoJournal · Filed · About .NET

AspNetCore shipped a fix for an intermittent parallel build failure that's been hitting developers during publish operations, while quietly upgrading its CI infrastructure across the board.

The team disabled compression in Microsoft.AspNetCore.App.Internal.Assets to kill a race condition where parallel publishes were fighting over the same shared `obj/compressed/publish` directory, causing "file is being used by another process" failures [1]. This is a quality-of-life fix that stops random build timeouts in CI and local development. On the infrastructure side, actions/cache/restore bumped to 6.1.0 with improved read-only cache handling [2], and dotnet/arcade pushed mirror configuration support for Alpine, Ubuntu, and Debian environments [3][4]. Google's test framework also got a minor update addressing name resolution in gMock [5]. None of these are breaking changes, but the compression fix is worth pulling in the next time you're rebuilding your build matrix.

Action items

References

  1. [1] Disable compression in Microsoft.AspNetCore.App.Internal.Assets ↗ dotnet/aspnetcore
  2. [2] [main] (deps): Bump actions/cache/restore from 5.0.5 to 6.1.0 ↗ dotnet/aspnetcore
  3. [3] [main] (deps): Bump dotnet/arcade/.github/workflows/inter-branch-merge-base.yml from 7013d9d28581f8597f7ddc73dcd79e4d91af866d to b8b677cf7d0e22a28f3a42b89e02527aa150a47b ↗ dotnet/aspnetcore
  4. [4] [main] (deps): Bump dotnet/arcade/.github/workflows/backport-base.yml from 7013d9d28581f8597f7ddc73dcd79e4d91af866d to b8b677cf7d0e22a28f3a42b89e02527aa150a47b ↗ dotnet/aspnetcore
  5. [5] [main] (deps): Bump src/submodules/googletest from `8b53336` to `973323e` ↗ dotnet/aspnetcore

FAQ

What changed in .NET on July 5, 2026?
AspNetCore shipped a fix for an intermittent parallel build failure that's been hitting developers during publish operations, while quietly upgrading its CI infrastructure across the board.
What should .NET teams do about it?
Pull the compression fix [ref:5] into your next AspNetCore update to eliminate parallel publish race conditions • Update actions/cache/restore to 6.1.0 on your next CI workflow refresh
Which .NET repositories shipped on July 5, 2026?
dotnet/aspnetcore

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.