[main] 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: f7901f87-9f24-40d6-9bc1-564863937237
• Build: 20250919.3 (284039)
• Date Produced: September 20, 2025 12:49:55 AM UTC
• Commit: 992bd27d60fa0ee11af65c89b31d71dc9ca7e18e
• Commit Diff: a795388...992bd27
• Branch: main

Updated Dependencies

• From 5.0.0-2.25468.102 to 5.0.0-2.25469.103
  • Microsoft.CodeAnalysis
  • Microsoft.CodeAnalysis.Analyzers
  • Microsoft.CodeAnalysis.CSharp
  • Microsoft.Net.Compilers.Toolset
• From 10.0.100-rc.2.25468.102 to 10.0.100-rc.2.25469.103
  • Microsoft.CodeAnalysis.NetAnalyzers
  • Microsoft.DotNet.ApiCompat.Task
  • Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100.Transport
• From 11.0.0-beta.25468.102 to 11.0.0-beta.25469.103
  • 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.25468.102 to 0.11.5-alpha.25469.103
  • Microsoft.DotNet.Cecil
• From 2.9.3-beta.25468.102 to 2.9.3-beta.25469.103
  • Microsoft.DotNet.XUnitAssert
  • Microsoft.DotNet.XUnitConsoleRunner
• From 10.0.0-rc.1.25468.102 to 10.0.0-rc.1.25469.103
  • 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 7.0.0-preview.1.46902 to 7.0.0-preview.1.47003
  • NuGet.Frameworks
  • NuGet.Packaging
  • NuGet.ProjectModel
  • NuGet.Versioning
• From 2.0.0-rc.1.25468.102 to 2.0.0-rc.1.25469.103
  • System.CommandLine

Associated changes in source repos

• dotnet/msbuild@36b870e...93d3372

[dotnet-maestro]

Important

The source repository has received code changes from an opposite flow. Any additional codeflows into this PR may potentially result in lost changes.
Please continue with one of the following options:

1. Close or merge this PR and let the codeflow continue normally
2. Close or merge this PR and receive the new codeflow immediately by triggering the subscription:
   darc trigger-subscriptions --id f7901f87-9f24-40d6-9bc1-564863937237
3. Force-flow new changes into this PR at your own risk (some PR commits might be reverted):
   darc trigger-subscriptions --force --id f7901f87-9f24-40d6-9bc1-564863937237

In case of unclarities, consult the FAQ or tag @dotnet/product-construction for assistance.

[tannergooding]

There's a lot of WASM timeouts here, with only 8.4% of tests passing

@dotnet/wasm-eng

[pavelsavara]

error NU1603: Warning As Error

Log

[] /root/helix/work/workitem/e/wbt artifacts/blz_no_workload_Debug_False_oaoy53cv_nub_鿀蜒枛遫䡫煉/App/BlazorBasicTestApp.csproj : 
error NU1603: Warning As Error: BlazorBasicTestApp depends on Microsoft.AspNetCore.App.Internal.Assets (>= 10.0.0-rc.1.25469.103) 
but Microsoft.AspNetCore.App.Internal.Assets 10.0.0-rc.1.25469.103 was not found. Microsoft.AspNetCore.App.Internal.Assets 10.0.0-rc.2.25416.105 was resolved instead.

[] /root/helix/work/workitem/e/wbt artifacts/blz_no_workload_Debug_False_oaoy53cv_nub_鿀蜒枛遫䡫煉/App/BlazorBasicTestApp.csproj : 
error NU1603: Warning As Error: BlazorBasicTestApp depends on Microsoft.NET.ILLink.Tasks (>= 10.0.0-rc.1.25469.103) 
but Microsoft.NET.ILLink.Tasks 10.0.0-rc.1.25469.103 was not found. Microsoft.NET.ILLink.Tasks 10.0.0-rc.2.25416.105 was resolved instead.

[maraf]

Looks like the SDK for WBT that flown in with this PR is referencing non-existent package version

[lewing]

Looks like the SDK for WBT that flown in with this PR is referencing non-existent package version

cc @ericstj

[ericstj]

Sorry @lewing I don't know too much about these tests other than they break a lot because they are trying to mix/match bits from the SDK to apply templates.

It does look like the PR description agrees with your findings, so you might have a look at the build that is being updated here to see if it published those packages and to which feed. I wonder if those are on the dotnet11 feeds and the tests aren't using those?

[kg]

Does this PR taking a while to get merged make dotnet-maestro think our repo is up to date now? Or does the next code flow just take a while before it's triggered? Wondering whether I need to manually trigger codeflow somehow so that #120074 can build (it needs the latest code from dotnet/arcade, which wasn't in this codeflow)

I read through the relevant docs I could find and grepped to try and find our codeflow configuration (couldn't find it) so I'm not sure how this works.