[release/8.0-staging] Update dependencies from dotnet/xharness

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/dotnet/xharness

• Subscription: 3c89df73-24a9-48a4-8224-08dbcfd3ad70
• Build: 20260112.2 (296897)
• Date Produced: January 12, 2026 1:41:10 PM UTC
• Commit: 185cb0f85ff4c3cb06b26610b068a079565893aa
• Branch: main

• Dependency Updates:
  • From 8.0.0-prerelease.25516.2 to 11.0.0-prerelease.26062.2
    • Microsoft.DotNet.XHarness.CLI
    • Microsoft.DotNet.XHarness.TestRunners.Common
    • Microsoft.DotNet.XHarness.TestRunners.Xunit

[jeffhandley]

@mmitche / @hoyosjs - These errors are unusual. Do you have guidance on this?

src/mono/wasm/symbolicator/WasmSymbolicator.csproj(0,0): error NU1605: Warning As Error: Detected package downgrade: Microsoft.Extensions.Logging from 8.0.1 to 6.0.0. Reference the package directly from the project to select a different version. WasmSymbolicator -> Microsoft.DotNet.XHarness.Common 11.0.0-prerelease.26062.2 -> Microsoft.Extensions.Logging (>= 8.0.1) WasmSymbolicator -> Microsoft.Extensions.Logging (>= 6.0.0)

[mmitche]

Xharness jumped forward to 11.0 in this PR. which seems wrong.

[mmitche]

All the xharness subscriptions are currently set to "Eng - Latest" for all runtime branches.

[mmitche]

@jeffhandley 3 weeks ago, the 9.0 staging branch appeared to have been pulling from .NET 9 Eng. Now it's pulling from Eng - Latest. DOes that update ring any bells?

[steveisok]

@jeffhandley @mmitche @dotnet/runtime-infrastructure what should we do here?

[mmitche]

I think close this and then fix the input channel.

[kotlarmilos]

All branches use the latest Apple mobile queues, which require the latest XHarness. Since we don’t test Apple mobile on older versions, we should keep the latest channel for all branches, as it is now.

[kotlarmilos]

Triggered the subscription again #124544