[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: b472297a-0d16-41ea-91af-ee5ed4325178
• Build: 20260415.14 (310568)
• Date Produced: April 15, 2026 10:20:47 PM UTC
• Commit: b61c1c319cf700db4bd4c7bbe9b2156c5383dd18
• Commit Diff: 0cf6b19...b61c1c3
• Branch: main

Removed Dependencies

• Removed 10.0.3
  • Microsoft.Extensions.DependencyInjection.Abstractions

Associated changes in source repos

• dotnet/aspnetcore@7cbda0e...bc03ef8
• dotnet/command-line-api@0b48ccb...d3de878
• dotnet/efcore@713aaf0...63572ec
• dotnet/fsharp@d507366...872352f
• dotnet/msbuild@8a330c4...e2ae904
• dotnet/razor@e626c1b...5813e6f
• dotnet/roslyn@f839a71...0eca297
• dotnet/runtime@1f4f1ff...cf7fcfa
• dotnet/sdk@1e5d8e3...7aa1db6
• dotnet/source-build-assets@66ddf29...b1d5d43
• dotnet/winforms@b1bb375...b8261ba

Diff the source with this PR branch

darc vmr diff --name-only https://github.com/dotnet/dotnet:b61c1c319cf700db4bd4c7bbe9b2156c5383dd18..https://github.com/dotnet/arcade:darc-main-a2de1e6a-87f5-430b-a566-a43bda0193fd

[dotnet-maestro]

Caution

🚨 Action Required — Conflict detected

A conflict was detected when trying to update this PR with changes from build 309919 of https://github.com/dotnet/dotnet/tree/5bed4499b04cbbaec57ac4209ae993acca3648cc.

The conflicts in the following files need to be manually resolved:

• src/Microsoft.DotNet.Arcade.Sdk/tools/DefaultVersions.props
  🔍 View file in dotnet/arcade vs VMR

ℹ️ To resolve the conflicts, please follow these steps:

1. Clone the current repository

   git clone https://github.com/dotnet/arcade
   cd arcade

2. Make sure your darc is up-to-date
   (version 1.1.0-beta.26202.1 or higher)

   # Linux / MacOS
   ./eng/common/darc-init.sh
   # or on Windows
   .\eng\common\darc-init.ps1

3. Run from repo's git clone and follow the instructions provided by the command to stage the conflict locally

   darc vmr resolve-conflict --subscription b472297a-0d16-41ea-91af-ee5ed4325178

   This should apply the build 309919 with sources from 5bed449
4. Resolve the conflicts, commit & push the changes
5. Once pushed, the Codeflow verification check will turn green.
   If not, a new build might have flown into the PR and you might need to run the command above again.

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

[dotnet-maestro]

Caution

🚨 Action Required — Conflict detected

A conflict was detected when trying to update this PR with changes from build 310323 of https://github.com/dotnet/dotnet/tree/b94d039caa166db357a3b806a4ec698e429f0cae.

The conflicts in the following files need to be manually resolved:

• src/Microsoft.DotNet.Arcade.Sdk/tools/DefaultVersions.props
  🔍 View file in dotnet/arcade vs VMR

ℹ️ To resolve the conflicts, please follow these steps:

1. Clone the current repository

   git clone https://github.com/dotnet/arcade
   cd arcade

2. Make sure your darc is up-to-date
   (version 1.1.0-beta.26214.2 or higher)

   # Linux / MacOS
   ./eng/common/darc-init.sh
   # or on Windows
   .\eng\common\darc-init.ps1

3. Run from repo's git clone and follow the instructions provided by the command to stage the conflict locally

   darc vmr resolve-conflict --subscription b472297a-0d16-41ea-91af-ee5ed4325178

   This should apply the build 310323 with sources from b94d039
4. Resolve the conflicts, commit & push the changes
5. Once pushed, the Codeflow verification check will turn green.
   If not, a new build might have flown into the PR and you might need to run the command above again.

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

[dotnet-maestro]

Caution

🚨 Action Required — Conflict detected

A conflict was detected when trying to update this PR with changes from build 310568 of https://github.com/dotnet/dotnet/tree/b61c1c319cf700db4bd4c7bbe9b2156c5383dd18.

The conflicts in the following files need to be manually resolved:

• src/Microsoft.DotNet.Arcade.Sdk/tools/DefaultVersions.props
  🔍 View file in dotnet/arcade vs VMR

ℹ️ To resolve the conflicts, please follow these steps:

1. Clone the current repository

   git clone https://github.com/dotnet/arcade
   cd arcade

2. Make sure your darc is up-to-date
   (version 1.1.0-beta.26214.2 or higher)

   # Linux / MacOS
   ./eng/common/darc-init.sh
   # or on Windows
   .\eng\common\darc-init.ps1

3. Run from repo's git clone and follow the instructions provided by the command to stage the conflict locally

   darc vmr resolve-conflict --subscription b472297a-0d16-41ea-91af-ee5ed4325178

   This should apply the build 310568 with sources from b61c1c3
4. Resolve the conflicts, commit & push the changes
5. Once pushed, the Codeflow verification check will turn green.
   If not, a new build might have flown into the PR and you might need to run the command above again.

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

[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 b472297a-0d16-41ea-91af-ee5ed4325178
  

• 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 b472297a-0d16-41ea-91af-ee5ed4325178 --force
  

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