[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: 20251104.4 (289521)
• Date Produced: November 4, 2025 7:16:29 PM UTC
• Commit: 8ee0cc0bbdbacfeb5b7e703909c9731ff75600f1
• Commit Diff: 79c85d9...8ee0cc0
• Branch: release/10.0.1xx

Updated Dependencies

• From 5.0.0-2.25515.111 to 5.0.0-2.25554.104
  • Microsoft.CodeAnalysis
  • Microsoft.CodeAnalysis.Analyzers
  • Microsoft.CodeAnalysis.CSharp
  • Microsoft.Net.Compilers.Toolset
• From 10.0.100 to 10.0.101
  • Microsoft.CodeAnalysis.NetAnalyzers
  • Microsoft.DotNet.ApiCompat.Task
• From 10.0.0-beta.25515.111 to 10.0.0-beta.25554.104
  • 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.25515.111 to 0.11.5-alpha.25554.104
  • Microsoft.DotNet.Cecil
• From 2.9.3-beta.25515.111 to 2.9.3-beta.25554.104
  • Microsoft.DotNet.XUnitAssert
  • Microsoft.DotNet.XUnitConsoleRunner
• From 10.0.0 to 10.0.1
  • 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.100-rtm.25515.111 to 10.0.101-servicing.25554.104
  • Microsoft.NET.Workload.Emscripten.Current.Manifest-10.0.100.Transport
• From 7.0.0-rc.1611 to 7.0.0-rc.5504
  • NuGet.Frameworks
  • NuGet.Packaging
  • NuGet.ProjectModel
  • NuGet.Versioning
• From 2.0.0 to 2.0.1
  • System.CommandLine
• From 10.0.0-prerelease.25527.1 to 10.0.0-prerelease.25506.2
  • Microsoft.DotNet.XHarness.CLI
  • Microsoft.DotNet.XHarness.TestRunners.Common
  • Microsoft.DotNet.XHarness.TestRunners.Xunit

Associated changes in source repos

• dotnet/arcade@e8ca693...fb1799f
• dotnet/aspnetcore@c697d89...7387de9
• dotnet/deployment-tools@c0c5287...84ccc05
• dotnet/diagnostics@53c7e6f...73f1fdc
• dotnet/efcore@209ba39...46842f5
• dotnet/emsdk@36bb709...2b402ca
• dotnet/msbuild@ef8ee47...149ded8
• dotnet/razor@48a2659...967dc4f
• dotnet/roslyn@7463b65...68a9207
• 9756c8e...f24c0d6
• dotnet/sdk@2ee5539...ce50bec
• dotnet/source-build-reference-packages@fdb961b...d39396d
• dotnet/templating@304a982...e3fa684
• microsoft/vstest@740c683...697c127
• dotnet/windowsdesktop@e2dc1b2...6d8c288
• dotnet/winforms@2b94716...aede76c
• dotnet/wpf@a94c8eb...3daa2ad

[steveisok]

@dotnet/runtime-infrastructure linker tests are failing with PackageReference System.Threading.AccessControl will not be pruned.. Are there supplemental changes coming that need to work their way through?

[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 74dc5d43-0b13-491a-b063-0f03b26d7664
3. Force-flow new changes into this PR at your own risk (some PR commits might be reverted):
   darc trigger-subscriptions --force --id 74dc5d43-0b13-491a-b063-0f03b26d7664

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

[akoeplinger]

@ericstj ^

[ericstj]

@akoeplinger This hack should be removed, like you did in main. 2abf811

Interesting that it took this long for that change to be observed by Mono.Linker.Tests.csproj. Those must not actually be building against the live product. Nevermind, I see why this just hit now. It was bugfix in RC2 that fixed the pruning data to include this package which moved down in 10.0. It does mean that these are building against SDK targeting pack instead of live built, which is probably an unfortunate design of this subset.

[ericstj]

Looks like this test is failing due to wrong RuntimeInformation.FrameworkDesciprtion. It would seem the validation build has a stable version but STABILIZE_PACKAGE_VERSION might not be set.

I grabbed a binlog and noticed -->
InformationalVersion = 10.0.1

This is happening because of this -->

runtime/Directory.Build.targets

Line 62 in b2842ae

<InformationalVersion Condition="'$(InformationalVersion)' == '' and '$(PreReleaseVersionLabel)' == 'servicing'">$(ProductVersion)</InformationalVersion>

And this PR changed the PreReleaseVersionLabel to servicing.

What's our expectation here?
#83311 changed this behavior - which has been around since 8.0.

It looks like 9.0 servicing set both

runtime/eng/Versions.props

Lines 17 to 18 in 9c2fb4b

	<StabilizePackageVersion Condition="'$(StabilizePackageVersion)' == ''">true</StabilizePackageVersion>
	<DotNetFinalVersionKind Condition="'$(StabilizePackageVersion)' == 'true'">release</DotNetFinalVersionKind>

While this is not set in 10.0

runtime/eng/Versions.props

Lines 18 to 19 in c1ad1c6

	<StabilizePackageVersion Condition="'$(StabilizePackageVersion)' == ''">false</StabilizePackageVersion>
	<DotNetFinalVersionKind Condition="'$(StabilizePackageVersion)' == 'true'">release</DotNetFinalVersionKind>

So maybe that's what we should do here, that would fix these tests, since they use this to control the behavior. @mmitche @akoeplinger ?