[release/10.0.1xx] Source code updates from microsoft/vstest

[dotnet-maestro]

Note

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

This pull request brings the following source code changes

From https://github.com/microsoft/vstest

• Subscription: e9328371-2231-4e19-8729-a16477127d8e
• Build: 20260224.1 (303171)
• Date Produced: February 24, 2026 2:17:13 PM UTC
• Commit: 936ecf0f49b8b069215aa7603dcfe5d164f7ef93
• Commit Diff: 697c127...936ecf0
• Branch: rel/18.0

Diff the source with this PR branch

darc vmr diff --name-only https://github.com/microsoft/vstest:936ecf0f49b8b069215aa7603dcfe5d164f7ef93..https://github.com/dotnet/dotnet:darc-release/10.0.1xx-d5062d1f-b4a3-40f0-8d25-90fa901d7e1e

[dotnet-maestro]

Note

PRs from original repository included in this codeflow update:

• [rel/18.0] Update build tools to 17.11.48 to be source buildable microsoft/vstest#15318
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15288
• Update MicrosoftInternalCodeCoveragePackageVersion to 18.0.6 microsoft/vstest#15312
• Update build tools to 17.8.43 microsoft/vstest#15305

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

[nohwnd]

This does not affect dotnet, this is for VS insertion.

[nohwnd]

This was automatic update from dotnet/dotnet, so not sure why it blocks the build here.

[mmitche]

Because it's pinned here https://github.com/dotnet/dotnet/pull/3809/files#diff-c1b405191bf88ac8d480e5a3b3d223cdb7d21b1580298b2c515d8c9c5e08cb05R9 to a specific version. vstest depends on diagnostics, but the pinning means that the version of diagnostics that is specified is not what the VMR is building, hence the pre-built.

The pinning should be removed for the NETCoreClient package.

[nohwnd]

This is update for compliance. It has no functional impact on the shipment.

[mmitche]

I think we can wait on this. No critical need for 10.0.102

[mmitche]

@nohwnd Please take a look at this when you get a chance for 10.0.3

[mmitche]

@nohwnd Ping on this.

[nohwnd]

microsoft/vstest#15355 removing the netcore client pinning here.

[nohwnd]

PR on the other side is merged, now it needs to propagate, all other branches (18.3, main) don't have the pinning.

[akoeplinger]

@nohwnd it looks like the most recent builds on https://dev.azure.com/dnceng/internal/_build?definitionId=1222&_a=summary have been failing for rel/18.0

[nohwnd]

Hopefully will fix after this is merged (it has the changes I had to do on other branches after the new policies #3809 (comment) )

[dotnet-maestro]

Note

PRs from original repository included in this codeflow update:

• Update branding to 18.0.2 microsoft/vstest#15320
• Remove pinning from NETCore.client microsoft/vstest#15355
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15367
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15378
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15384
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15388
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15391
• [rel/18.0] Update dependencies from dotnet/arcade microsoft/vstest#15390

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

[akoeplinger]

there's still an error related to the diagnostics package

[dotnet-maestro]

Note

PRs from original repository included in this codeflow update:

• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15406
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15408
• [rel/18.0] Source code updates from dotnet/dotnet microsoft/vstest#15411

💡 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 e9328371-2231-4e19-8729-a16477127d8e
  

• 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 e9328371-2231-4e19-8729-a16477127d8e --force
  

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

[nohwnd]

triggered new one

[nohwnd]

there's still an error related to the diagnostics package

That is weird, those updates are coming from dotnet/dotnet (not just this PR, but basically we don't touch the rel branch after releasing, only automatic insertions keep updating it). microsoft/vstest#15420

[nohwnd]

#5082 the new PR

[akoeplinger]

ok looks like #5082 is green :)