RepoJournal
.NET

@dotnet

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

Pick a date

The Wire · Showcase

DOTNET-OPERATOR-SDK BREAKS LABEL SELECTORS. ARM64 GETS PAC-RET SECURITY. RUNTIME KILLS PROLOG LIMITS.

By RepoJournal · Filed · About .NET

Kubernetes client namespaces are renamed in v11.0.0, Arm64 JIT now supports pointer authentication to block ROP attacks, and the runtime removes the single instruction group prolog restriction that's been choking optimization for years.

The dotnet-operator-sdk shipped v11.0.0 with breaking changes [1]: the `LabelSelectors` namespace is now `Selectors`, and `DefaultEntityLabelSelector` is sealed instead of public. If you subclass that selector, your build breaks. On the security front, runtime PR [2] lands Pointer Authentication (PAC) support for Arm64, a cryptographic defense against Return-Oriented Programming attacks via signed return addresses. This is Armv8.3+ hardware security you can actually use now. Simultaneously, the JIT landed a major optimization unlock [3]: removing the single-IG prolog restriction that forced jumps to encode destinations as relative offsets. Compilers can now generate smarter instruction groups without artificial constraints. The runtime also dropped obsolete ARMV7L CMake defines [5], cleaning up dead code. On the skills desk, dotnet-msbuild now registers the AITools.BinlogMcp MCP server [4], pulling from the dotnet-eng public feed and rewiring binlog-failure-analysis to call it. MSBuild enlightened the RAR task [6] to absolutize more inputs, fixing audit gaps in build logs.

Action items

References

  1. [1] v11.0.0 ↗ dotnet/dotnet-operator-sdk
  2. [2] Arm64: [PAC-RET] Jit Support ↗ dotnet/runtime
  3. [3] [RyuJit] Remove the single-IG prolog restriction (#126552) dotnet/runtime
  4. [4] dotnet-msbuild: register AITools.BinlogMcp and use it from binlog-failure-analysis ↗ dotnet/skills
  5. [5] Remove obsolete ARMV7L CMake defines (#128199) dotnet/runtime
  6. [6] Enlighten RAR task ↗ dotnet/msbuild

FAQ

What changed in .NET on May 20, 2026?
Kubernetes client namespaces are renamed in v11.0.0, Arm64 JIT now supports pointer authentication to block ROP attacks, and the runtime removes the single instruction group prolog restriction that's been choking optimization for years.
What should .NET teams do about it?
Pin dotnet-operator-sdk upgrade until you rename LabelSelectors namespaces and stop subclassing DefaultEntityLabelSelector • Test Arm64 workloads with PAC-RET JIT support enabled if you run Armv8.3+ hardware • Review MSBuild RAR task enlightenment if you rely on build log auditing for deployment validation
Which .NET repositories shipped on May 20, 2026?
dotnet/dotnet-operator-sdk, dotnet/runtime, dotnet/skills, dotnet/msbuild

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.