[release/10.0] Source code updates from dotnet/dotnet

[dotnet-maestro]

Note

This is a codeflow update. It may contain both source code changes from
the VMR
as well as dependency updates. Learn more here.

This pull request brings the following source code changes

From https://github.com/dotnet/dotnet

• Subscription: 74dc5d43-0b13-491a-b063-0f03b26d7664
• Build: 20260112.8 (297004)
• Date Produced: January 13, 2026 5:14:26 AM UTC
• Commit: 976695d40cfde0801c78b8fed85ca80e997da085
• Commit Diff: 4ef9fba...976695d
• Branch: release/10.0.1xx

Updated Dependencies

• From 5.0.0-2.26057.111 to 5.0.0-2.26062.108
  • Microsoft.CodeAnalysis
  • Microsoft.CodeAnalysis.Analyzers
  • Microsoft.CodeAnalysis.CSharp
  • Microsoft.Net.Compilers.Toolset
• From 10.0.103 to 10.0.103
  • Microsoft.CodeAnalysis.NetAnalyzers
  • Microsoft.DotNet.ApiCompat.Task
• From 10.0.0-beta.26057.111 to 10.0.0-beta.26062.108
  • Microsoft.DotNet.Arcade.Sdk
  • Microsoft.DotNet.Build.Tasks.Archives
  • Microsoft.DotNet.Build.Tasks.Feed
  • Microsoft.DotNet.Build.Tasks.Installers
  • Microsoft.DotNet.Build.Tasks.Packaging
  • Microsoft.DotNet.Build.Tasks.TargetFramework
  • Microsoft.DotNet.Build.Tasks.Templating
  • Microsoft.DotNet.Build.Tasks.Workloads
  • Microsoft.DotNet.CodeAnalysis
  • Microsoft.DotNet.GenAPI
  • Microsoft.DotNet.GenFacades
  • Microsoft.DotNet.Helix.Sdk
  • Microsoft.DotNet.PackageTesting
  • Microsoft.DotNet.RemoteExecutor
  • Microsoft.DotNet.SharedFramework.Sdk
  • Microsoft.DotNet.XliffTasks
  • Microsoft.DotNet.XUnitExtensions
• From 0.11.5-alpha.26057.111 to 0.11.5-alpha.26062.108
  • Microsoft.DotNet.Cecil
• From 2.9.3-beta.26057.111 to 2.9.3-beta.26062.108
  • Microsoft.DotNet.XUnitAssert
  • Microsoft.DotNet.XUnitConsoleRunner
• From 10.0.3 to 10.0.3
  • Microsoft.NET.Sdk.IL
  • Microsoft.NETCore.App.Ref
  • Microsoft.NETCore.ILAsm
  • runtime.native.System.IO.Ports
  • System.Reflection.Metadata
  • System.Reflection.MetadataLoadContext
  • System.Text.Json
• From 10.0.103-servicing.26057.111 to 10.0.103-servicing.26062.108
  • Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100.Transport
• From 7.0.2-rc.5811 to 7.0.2-rc.6308
  • NuGet.Frameworks
  • NuGet.Packaging
  • NuGet.ProjectModel
  • NuGet.Versioning
• From 2.0.3 to 2.0.3
  • System.CommandLine

Associated changes in source repos

• dotnet/arcade@d8dca0b...9f518f2
• dotnet/aspnetcore@991f0cb...8b982fb
• df5d2d2...95a8439
• dotnet/sdk@dde80f2...400e46e
• dotnet/templating@0cac1aa...bcb12af
• dotnet/windowsdesktop@2e44b04...c2987dd
• dotnet/winforms@6f75668...f016950

Diff the source with this PR branch

darc vmr diff --name-only https://github.com/dotnet/dotnet:976695d40cfde0801c78b8fed85ca80e997da085..https://github.com/dotnet/runtime:darc-release/10.0-9f962efb-b142-4962-a889-b816d8a49a0c

[maraf]

It is a race condition in the test. My guess it's caused by browser trying to fetch favicon. Backporting #122775 will help The test matching only .wasm requests

[dotnet-maestro]

Important

While this PR was open, the source repository has received code changes from this repository (an opposite codeflow merged).
To avoid complex conflicts, the codeflow cannot continue until this PR is closed or merged.

You can continue with one of the following options:

• Ignore this and merge this PR as usual without waiting for the new changes.
  Once merged, Maestro will create a new codeflow PR with the new changes.
• Close this PR and wait for Maestro to open a new one with old and new changes included.
  You will lose any manual changes made in this PR.
  You can also manually trigger the new codeflow right away by running:

  darc trigger-subscriptions --id 74dc5d43-0b13-491a-b063-0f03b26d7664
  

• Force a codeflow into this PR at your own risk if you want the new changes.
  User commits made to this PR might be reverted.

  darc trigger-subscriptions --id 74dc5d43-0b13-491a-b063-0f03b26d7664 --force
  

💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance.

[oroztocil]

Likely cause of AssetCachingTest is race condition in passing stdout from the server app process to the test process. We will try to make the test deterministic by chaning the method of getting server logs to the test code.