[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/dotnet/winforms

• Subscription: 911109f6-9cf9-4d74-be88-9b5d1e534f52
• Build: 20261009.5 (335972)
• Date Produced: October 9, 2026 9:37:00 PM UTC
• Commit: 77d6ad34245145ef48077dda241343787153ce43
• Commit Diff: 73d1349...77d6ad3
• Branch: main

Diff the source with this PR branch

darc vmr diff --name-only https://github.com/dotnet/winforms:77d6ad34245145ef48077dda241343787153ce43..https://github.com/dotnet/dotnet:darc-main-46ee3ca2-db66-47f7-a6f0-1ef2adfe5205

[dotnet-maestro]

Note

PRs from original repository included in this codeflow update:

• [main] Source code updates from dotnet/dotnet winforms#15242
• [main] Source code updates from dotnet/dotnet winforms#15250
• minor spelling changes in comments winforms#15246
• Spellchecked winforms#15247

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

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[maestro-approver]

This pull request contains only source updates from https://github.com/dotnet/winforms.

• Commit Diff: 73d1349...77d6ad3

[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 911109f6-9cf9-4d74-be88-9b5d1e534f52
  

• 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 911109f6-9cf9-4d74-be88-9b5d1e534f52 --force
  

💡 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 911109f6-9cf9-4d74-be88-9b5d1e534f52
  

• 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 911109f6-9cf9-4d74-be88-9b5d1e534f52 --force
  

💡 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 911109f6-9cf9-4d74-be88-9b5d1e534f52
  

• 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 911109f6-9cf9-4d74-be88-9b5d1e534f52 --force
  

💡 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 911109f6-9cf9-4d74-be88-9b5d1e534f52
  

• 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 911109f6-9cf9-4d74-be88-9b5d1e534f52 --force
  

💡 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 911109f6-9cf9-4d74-be88-9b5d1e534f52
  

• 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 911109f6-9cf9-4d74-be88-9b5d1e534f52 --force
  

💡 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 911109f6-9cf9-4d74-be88-9b5d1e534f52
  

• 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 911109f6-9cf9-4d74-be88-9b5d1e534f52 --force
  

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

[akoeplinger]

@copilot open a new PR to remove this accidentally committed file