RepoJournal
.NET

@dotnet

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

Pick a date

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

The Wire · Showcase

RUNTIME PATCHES ARRAYPOOL LEAK, ISSUE-LABELER GAINS DISCUSSION SUPPORT

By RepoJournal · Filed · About .NET

A critical ArrayPool fix lands in dotnet/runtime while issue-labeler v2.1.0 extends ML-powered labeling to GitHub Discussions.

The runtime team shipped a fix for ArrayPool rent operations missing try/finally blocks [1], preventing resource leaks in high-throughput scenarios. In parallel, PackageOverrides.txt now includes 27 missing meta-packages and RID-selector packages [2], closing gaps in NuGet pruning for legacy framework versions (netcoreapp1.0 through netstandard2.0). On the JIT front, two optimization PRs landed: GenTreeIntCon fields are now private with accessor enforcement [3] for safer debugging, and range check overflow caching has been cleaned up to remove the per-node OverflowMap [4], simplifying bounds check logic. Issue-labeler v2.1.0 [7] ships with two major features: discussion labeling now works alongside issue labeling [8], letting teams auto-label GitHub Discussions using the same ML pipeline, and a new max_labels input [9] enables multi-label predictions instead of single-label stops. Nerdbank.Streams saw routine dependency updates including StreamJsonRpc 2.25.28 [5] and .NET packages bumped to 10.0.9 [6].

Action items

References

  1. [1] Fix Arraypool rent without try/finally block ↗ dotnet/runtime
  2. [2] Add missing meta-packages and binary-free packages to PackageOverrides.txt ↗ dotnet/runtime
  3. [3] JIT: encapsulate all fields in GenTreeIntCon ↗ dotnet/runtime
  4. [4] JIT: Clean up range check overflow caching and bounds check special cases (#129253) dotnet/runtime
  5. [5] Update dependency StreamJsonRpc to 2.25.28 ↗ dotnet/Nerdbank.Streams
  6. [6] Update .NET packages to 10.0.9 ↗ dotnet/Nerdbank.Streams
  7. [7] v2.1.0 ↗ dotnet/issue-labeler
  8. [8] Add discussion labeling to issues labeler workflow ↗ dotnet/issue-labeler
  9. [9] Add multi-label prediction support via max_labels input ↗ dotnet/issue-labeler

FAQ

What changed in .NET on June 13, 2026?
A critical ArrayPool fix lands in dotnet/runtime while issue-labeler v2.1.0 extends ML-powered labeling to GitHub Discussions.
What should .NET teams do about it?
Review ArrayPool usage in pooled code paths and test under load after upgrading runtime • Pin issue-labeler to v2.1.0-release SHA if using discussion labeling in your workflows • Validate PackageOverrides.txt correctness for legacy framework restore tests
Which .NET repositories shipped on June 13, 2026?
dotnet/runtime, dotnet/Nerdbank.Streams, dotnet/issue-labeler

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.