Who contributed to .NET on August 22, 2026?

6 developers shipped this update, including dkurepa, dotnet-maestro, simonrozsival, jonathanpeppers, jonpryor, and Redth.

What were the notable .NET updates?

[FastDeploy2] Clean orphan staging files, [FastDeploy2] Clean orphan staging files (#12310), and [build] Avoid staging unchanged framework assemblies.

@dotnet

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

github ↗

Pick a date

Topics: .NET Full archive →

The Wire · Showcase

Android CI tightens the net

By RepoJournal · Filed 07:00 UTC on August 22, 2026 · About .NET

6 people shipped this

dotnet-maestro @dotnet-maestro 4 cited

simonrozsival @simonrozsival 2 cited

jonathanpeppers @jonathanpeppers 2 cited

Redth @Redth 2 cited

dkurepa @dkurepa 1 cited

jonpryor @jonpryor 1 cited

The .NET Android team is hardening the deployment pipeline, and skipping unchanged framework assemblies could be the biggest win you're not expecting.

The .NET Android team shipped a batch of CI and tooling fixes aimed at making builds faster and deployments cleaner. The FastDeploy2 cleanup [1] [2] now strips orphaned staging directories after every successful APK install, and it fails closed on malformed `pm` output, which means you won't get subtle state corruption from a half-dead cleanup step. For Debug/no-shrink builds, unchanged framework assemblies are now packaged straight from their runtime-pack locations, skipping Cecil processing and project-local copies [3]. That cuts I/O significantly on clean MAUI Debug builds, though the PR notes Mono.Android and Java.Interop still go through full processing. On the testing side, a new Helix job builds and runs a MAUI template with CoreCLR full ReadyToRun for android-arm [4], closing the coverage gap for that configuration. Meanwhile, API 37.1 gets stabilized and enumified via BindingStudio [5], which sets the groundwork for consuming the latest Android SDK binding. The dotnet tool version in MAUI also moves from 10.0.108 to 10.0.111 [6] [7], a routine bump but worth noting if you're pinning exact SDK versions. Across the three repos, 17 commits and 19 PRs landed, most of them codeflow updates pulling in changes from arcade, nuget.client, roslyn, and fsharp into the monorepo [8] [9] [10] [11]. The runtime PR [12] appears to be a straightforward main merge, so nothing to panic about there. Skip the noise and focus on the deployment pipeline fixes.

Action items

→ Rebuild your MAUI Debug targets with the latest dotnet/maui to verify the framework assembly packaging change doesn't break your incremental builds dotnet/maui [plan]
→ Watch the FastDeploy2 cleanup behavior on your test devices; if you rely on manual staging paths, make sure they aren't symlinked dotnet/android [monitor]
→ Prepare for the API-37.1 binding update if you target the newest Android SDK; validate your binding usage against the new enum mappings dotnet/android [plan]

References

[1] [FastDeploy2] Clean orphan staging files ↗ dotnet/android
[2] [FastDeploy2] Clean orphan staging files (#12310) dotnet/android
[3] [build] Avoid staging unchanged framework assemblies ↗ dotnet/android
[4] [ci] Add MAUI full R2R android-arm Helix test ↗ dotnet/android
[5] [Mono.Android] Enumify, stabilize API-37.1 ↗ dotnet/android
[6] Update dotnet version from 10.0.108 to 10.0.111 ↗ dotnet/maui
[7] Update dotnet version from 10.0.108 to 10.0.111 (#37721) dotnet/maui
[8] [main] Source code updates from dotnet/arcade ↗ dotnet/dotnet
[9] [main] Source code updates from nuget/nuget.client ↗ dotnet/dotnet
[10] [main] Source code updates from dotnet/roslyn ↗ dotnet/dotnet
[11] [main] Source code updates from dotnet/fsharp ↗ dotnet/dotnet
[12] FF main runtime ↗ dotnet/dotnet

Quick answers

What shipped in .NET on August 22, 2026?: The .NET Android team is hardening the deployment pipeline, and skipping unchanged framework assemblies could be the biggest win you're not expecting. In total, 17 commits and 19 pull requests landed.
Who contributed to .NET on August 22, 2026?: 6 developers shipped this update, including dkurepa, dotnet-maestro, simonrozsival, jonathanpeppers, jonpryor, and Redth.
What were the notable .NET updates?: [FastDeploy2] Clean orphan staging files, [FastDeploy2] Clean orphan staging files (#12310), and [build] Avoid staging unchanged framework assemblies.

Kestrel blocks malformed SNI hostnames

Kestrel now rejects malformed SNI server names, closing a DNS-label-boundary hole in the TLS handshake.

dotnet 80 shipped

@dotnet Aug 20

SIGNALR CLOSES DUPLICATE STREAM HOLE

A protocol-invalid duplicate stream ID could leave the displaced hub argument permanently unreachable, and now it's rejected immediately.

dotnet 131 shipped

@dotnet Aug 19

MAUI Overhauls NuGet Publishing as FSharp Preps for VS 18.11

MAUI is replacing its custom NuGet publishing with Microsoft's 1ES.PublishNuget, and FSharp is rolling Microsoft.Build deps forward to VS 18.11, two moves that reshape release engineering across the .NET ecosystem.

dotnet 46 shipped

@dotnet Aug 18

MSBuild's telemetry failure can kill your build

A NullReferenceException in MSBuild's telemetry disposal is silently taking down .NET Framework builds.

dotnet 49 shipped

Elsewhere on the wire

AI Agents Aug 22

Cline hubs get drain and replay as Langchain plumb gates

Cline just shipped rollover-grade hub commands while Langchain exposes gateway internals, and OpenHands quietly broke its own monitoring contract.

ai-agents 42 shipped

Local LLMs Aug 22

SGLang ships v0.5.18 with 710 PRs and DeepSeek V4 FP4 auto-routing

The biggest release of the week just landed: SGLang v0.5.18 adds new models, fixes a silent disagg bug, and defaults DeepSeek V4 FP4 checkpoints to the right MoE runner.