[main] Update dependencies from microsoft/dcp

[dotnet-maestro]

This pull request updates the following dependencies

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

• Subscription: ca933625-6bed-4cef-95d3-a9cff8f51c9d
• Build: 0.26.2 (332145)
• Date Produced: September 15, 2026 6:03:38 PM UTC
• Commit: b9830ac8d11bd85d866ccbaf65783462f6f25742
• Branch: refs/tags/v0.26.2

• Dependency Updates:
  • From 0.25.13 to 0.26.2
    • Microsoft.DeveloperControlPlane.darwin-amd64
    • Microsoft.DeveloperControlPlane.darwin-arm64
    • Microsoft.DeveloperControlPlane.linux-amd64
    • Microsoft.DeveloperControlPlane.linux-arm64
    • Microsoft.DeveloperControlPlane.linux-musl-amd64
    • Microsoft.DeveloperControlPlane.windows-amd64
    • Microsoft.DeveloperControlPlane.windows-arm64

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20146

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20146"

[github-actions]

Tests selector

Selects the full PR test matrix + all PR-gated jobs (ALL) — a rule matching 'eng/Version.Details.xml' selects ALL

---

Selection computed for commit b212ab4.

[github-actions]

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

[aspire-repo-bot]

✅ No documentation update needed.

Step 5 branch taken: docs_optional -> dependency_bump

Triggered signals: none (signal_count = 0). signals.json shows recommendation: "docs_optional" with an empty triggered_signals list and only_test_or_build_changes: true.

Allowlist justification (dependency_bump): Both changed files are package/dependency version manifests with no behavior or surface change introduced by this PR itself:

• eng/Version.Details.xml (14 additions / 14 deletions) - version bump of Microsoft.DeveloperControlPlane.* RID-specific packages from 0.25.13 to 0.26.2.
• eng/Versions.props (7 additions / 7 deletions) - corresponding version property updates.

This is an automated Maestro dependency-flow PR (author: dotnet-maestro[bot]) that only bumps the DCP (Developer Control Plane) package versions consumed internally by Aspire. It introduces no new CLI options, public APIs, CLI/MCP tools, dashboard endpoints, container image tags, templates, or user-facing strings, and the PR body contains no user-facing/breaking-change/deprecation/security markers. No documentation update on microsoft/aspire.dev is warranted for this change.

[github-actions]

⚠️ CI Failure Analysis: Possible Flaky Test(s)

The CI build failed due to test failure(s) that appear unrelated to the PR changes. These may be flaky tests.

Suspected flaky test(s):

• Aspire Blazor browser debugger E2E hits a managed breakpoint for standalone in job Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, browser-debugger)
  • Error: Failed to apply E2E control revision 1789507121544: Error: Timed out after 285622ms waiting for pwa-msedge child session for Blazor WASM root '6520f58a-9374-46e8-bb31-50591765521f'. Last error: .
  • Stack Trace (first frames):

Error: Failed to apply E2E control revision 1789507121544: Error: Timed out after 285622ms waiting for pwa-msedge child session for Blazor WASM root '6520f58a-9374-46e8-bb31-50591765521f'. Last error: <none>. State: {"debugSessions":[{"id":"efcf0f3f-d1d2-43f3-8f19-3cb69ccd8eb4","type":"monovsdbg_wasm","name":"Wasm Managed Debugger", ...}]}

• Why likely flaky: Matches a known recurring pattern (13 prior occurrences, last seen 2026-09-15) of the browser-debugger E2E shard timing out waiting for the pwa-msedge child debug session to attach. This is a debugger-attach timing issue unrelated to the PR, which only bumps dependency versions in eng/Version.Details.xml and eng/Versions.props.
• Aspire dynamic debug configuration E2E "after each" hook for "re-resolves the selected AppHost by dynamic configuration name in duplicate-alias workspaces" in job Tests / Run VS Code extension E2E tests / VS Code extension E2E (Windows, dynamic-debug-configuration)
  • Error: Dynamic debug configuration E2E teardown failed.

1. Error: EBUSY: resource busy or locked, rmdir 'C:\Users\runneradmin\AppData\Local\Temp\aev-j1WByU\workspace.e2e-dynamic-debug\first'

• Stack Trace (first frames):

AggregateError: Dynamic debug configuration E2E teardown failed.
1. Error: EBUSY: resource busy or locked, rmdir 'C:\Users\runneradmin\AppData\Local\Temp\aev-j1WByU\workspace\.e2e-dynamic-debug\first'
    at runE2eTeardown (out\test-e2e\test-e2e\helpers\fixtures.js:217:15)
    at async Context.<anonymous> (out\test-e2e\test-e2e\dynamicDebugConfiguration.e2e.test.js:62:9)

• Why likely flaky: Matches a known recurring pattern (23 prior occurrences, last seen 2026-09-14) of the dynamic-debug-configuration E2E shard teardown failing with an EBUSY Windows file-locking race when removing the temp workspace directory. This is an environment/timing issue unrelated to the PR's dependency version bump.

Suggested actions:

• Re-run the failed CI jobs to confirm if the failure is intermittent
• If the test continues to fail, consider quarantining it using /quarantine-test <test name> <issue URL>
• Search existing issues to see if this test is already known to be flaky

You can re-run the failed jobs from the workflow run page.