$ the-wire · showcase
ASP.NET Core Ships Passkey Endpoints
By RepoJournal · Filed · About .NET
ASP.NET Core has landed native passkey support in the main branch.
ASP.NET Core has landed native passkey support in the main branch [1], bringing well-known endpoints and WebAuthn signals into the framework. This is the upgrade you've been waiting for, but it's experimental, so plan your adoption carefully. Meanwhile, Orleans is hardening its test suite, propagating cancellation tokens throughout to fix flaky waits [2] and suppressing warnings in generated code [3], which should clean up builds that treat warnings as errors. Arcade is shedding dead weight, removing the custom BuildTask base class [4] and five unused build tasks [5], simplifying task projects that source-include the removed code. Output caching also got a fix for a query-string cache-key collision [6]. Finally, MAUI fixed a flaky memory test by waiting for the in-app GC operation to complete, since the label displays "Checking..." for up to five seconds [7].
Action items
- → Review the experimental passkey endpoints in ASP.NET Core and track the diagnostic ASP0039 dotnet/aspnetcore [plan]
- → If using Orleans, verify your test suites benefit from cancellation propagation and regenerated code dotnet/orleans [monitor]
- → If your repo consumes the removed Arcade build tasks, check for breakage and update accordingly dotnet/arcade [immediate]
- → Pull the output caching collision fix into your ASP.NET Core dependencies dotnet/aspnetcore [plan]
References
- [1] Add well-known passkey endpoints and WebAuthn signals support ↗ dotnet/aspnetcore
- [2] fix(test): propagate xUnit cancellation ↗ dotnet/orleans
- [3] fix(codegen): suppress warnings in generated source ↗ dotnet/orleans
- [4] Remove the custom BuildTask base class ↗ dotnet/arcade
- [5] Remove unused build tasks ↗ dotnet/arcade
- [6] Fix Output Caching query-string cache-key collision ↗ dotnet/aspnetcore
- [7] [Flaky] Fixed the Issue34975 flaky issue ↗ dotnet/maui
