The Wire · Showcase
ASP.NET Core fixes JSON exception handling in minimal APIs
By RepoJournal · Filed · About .NET
JsonException now propagates correctly through problem details middleware instead of being swallowed, fixing a critical edge case in minimal API error handling.
The ASP.NET Core team shipped a fix [1] that lets JsonException bubble through problem details in minimal APIs, addressing a gap where malformed JSON payloads were being masked by the middleware. This one matters if you're relying on precise error signals in production. Over in F# land, the team is tightening up code review automation: they've moved CCR opt-out detection from labels to PR body comments [2], a pragmatic fix since the Copilot agent doesn't have access to label context anyway. They're also bumping the .NET SDK from 10.0.202 to 10.0.204 [3], so if you're building F# on CI, sync your images. The ASP.NET Core signing layer picked up a small but important change [4] adding catalog signing for .cat files covering customer-modifiable JS templates, keeping compliance aligned across the pipeline. Dependency updates across both repos are routine: gh-aw-actions bumped from 0.74.9 to 0.75.0 [5] and some stale version comments in GitHub Actions workflows got corrected [6] to match what Dependabot actually updated.
Action items
- → Review and test JSON error handling in minimal APIs if you use custom problem details middleware dotnet/aspnetcore [plan]
- → Sync F# builds to .NET SDK 10.0.204 in CI/CD dotnet/fsharp [plan]
- → Update any CCR opt-out instructions in F# PRs to use 'SKIP CCR REVIEW' in PR body instead of labels dotnet/fsharp [monitor]
References
- [1] Let JsonException bubble through problem details in minimal APIs ↗ dotnet/aspnetcore
- [2] Switch CCR opt-out to check PR body for 'SKIP CCR REVIEW' ↗ dotnet/fsharp
- [3] Bump system versions ↗ dotnet/fsharp
- [4] Add .cat catalog signing and update .js exclusion comment (#66443) dotnet/aspnetcore
- [5] [main] (deps): Bump github/gh-aw-actions from 0.74.9 to 0.75.0 ↗ dotnet/aspnetcore
- [6] Fix outdated version comments in GitHub Action workflows (#66776) dotnet/aspnetcore
FAQ
- What changed in .NET on May 23, 2026?
- JsonException now propagates correctly through problem details middleware instead of being swallowed, fixing a critical edge case in minimal API error handling.
- What should .NET teams do about it?
- Review and test JSON error handling in minimal APIs if you use custom problem details middleware • Sync F# builds to .NET SDK 10.0.204 in CI/CD • Update any CCR opt-out instructions in F# PRs to use 'SKIP CCR REVIEW' in PR body instead of labels
- Which .NET repositories shipped on May 23, 2026?
- dotnet/aspnetcore, dotnet/fsharp