RepoJournal
.NET @dotnet
107 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-08-02
stories 12
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

RUNTIME HARDENS UNSAFE CALLS WHILE MAUI FIXES MERGE PIPELINE

By RepoJournal · Filed · About .NET · Composed from the cited sources · methodology

EgorBo Shane Neuville Theodore Tsirpanis Copilot jkotas
5 people shipped this
EgorBo @EgorBo 2 cited Shane Neuville @PureWeen 2 cited Theodore Tsirpanis @teo-tsirpanis 1 cited Copilot @Copilot 1 cited jkotas @jkotas

The CLR just shipped tooling to migrate LibraryImport toward unsafe-v2, plus allocation cuts in COM interop, while MAUI plugs gaps in its bot-driven merge policy.

EgorBo landed the big one: LibraryImportGenerator now participates in C#'s new unsafe-evolution rules [1], complete with an analyzer and code-fixer to automatically add `unsafe` keywords to existing [LibraryImport] calls that lacked safety annotations [2]. Nothing breaks under unsafe-v1, but this is the tooling your team needs before unsafe-v2 becomes the default. On the allocation front, Theodore Tsirpanis eliminated temporary array allocations in ComVariant.As by using `params ReadOnlySpan<VarEnum>` to reference RVA fields directly [3], a small win that compounds across high-traffic P/Invoke paths. Over in MAUI, two follow-ups landed on merge automation: PureWeen closed post-merge review findings on the finalize step [4], and fixed the bot-opened inter-branch policy to stop redundantly checking issue authors [5]. The team also ripped out blanket integration-test retries after discovering 98.2% of them reproduced identical failures anyway, cutting noise from the pipeline [6].

$ ls dotnet/reviews/ # the step-back reads

the week in review CVE-2026-69304 hits ASP.NET Core; Spark 4.0 support lands the month in review F# interpolated strings and record spreads land as Orleans and runtime harden
Full archive → Weekly reviews →

Quick answers

What shipped in .NET on August 2, 2026?
The CLR just shipped tooling to migrate LibraryImport toward unsafe-v2, plus allocation cuts in COM interop, while MAUI plugs gaps in its bot-driven merge policy. In total, 6 commits and 6 pull requests landed.
Who contributed to .NET on August 2, 2026?
5 developers shipped this update, including EgorBo, Theodore Tsirpanis, jkotas, Shane Neuville, and Copilot.
What were the notable .NET updates?
Support unsafe evolution in LibraryImportGenerator, Support unsafe evolution in LibraryImportGenerator (#131245), and Remove temporary array allocations in `ComVariant.As`. (#131704).
♥

$ log @dotnet --recent

Vector literals stop breaking under comma-decimal cultures, AIDL one-way proxies generate correctly 83 shipped Spark 4.0 lands in .NET bindings, arcade refreshes Entra tokens mid-job 23 shipped MSBuild TaskAnalyzer quiets three diagnostics, Terminal Logger stops corrupting shared log events 20 shipped MAUI backports iOS regression coverage, aspnetcore bumps extensions 6 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training GSM8K scoring parses answers as exact decimals AI Red Teaming PyRIT closes a judge-spoofing hole, promptfoo accepts Langfuse v6

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.