Skepra / Web recovery & resilience

Aspire troubleshooting guide

When a client integration build stops, repeatedly updating tools can hide which component owns the failure. Start with the failing command and its environment, then separate version alignment, runtime readiness and security maintenance.

Discuss the next maintenance decision

Capture a useful build handoff

Ask the build owner for the failing command, its phase, the operating system and architecture, the installation channel, the CLI selected by that runner, and the SDK version configured by the project. Keep output limited to the error and relevant version evidence; do not include credentials or private feed configuration. Separate a developer workstation from the CI runner and from a running production service.

The same project name does not prove they execute the same tool installation.

Classify the symptom before changing the project

The Aspire guide distinguishes container-runtime readiness, port conflicts, service connectivity and CLI/SDK version mismatch. For a runtime wait, have the operator establish whether the required runtime is ready. For a port conflict, identify the owning service before stopping anything.

For a connection failure, inspect the declared service references and startup ordering. For code-generation mismatch, compare the installed CLI with the configured SDK before proposing a project-wide upgrade.

CLI alignment and security maintenance are different checks

Aspire documents errors when a selected SDK is newer than the installed CLI. Its update instructions depend on how the CLI was installed. Record both sides of the comparison and obtain the corresponding installation-channel procedure.

A successful project dependency update alone does not establish which executable a shared runner selects. After an approved tool change, repeat the original command and compare the generated SDK and integration behavior using synthetic fixtures.

Check CVE-2026-120778 on the right package lane

Microsoft published CVE-2026-120778 on 10 November 2026. For the listed npm Aspire CLI packages, the affected range is >=13.4.2 and <13.6.5; the fix is 13.6.5. On Linux or macOS, a local attacker able to influence MSBuild response-file discovery through a writable directory can affect a CLI-generated build.

The notice includes SDK generation, dump and export operations. This is a conditional local-build issue, not evidence of remote compromise of a website.

Verify the installation unit

For npm installations, Microsoft requires both @microsoft/aspire-cli and the platform-specific dependency to resolve to 13.6.5 or later. NuGet and standalone packages have their own affected ranges in the notice; do not copy the npm boundary onto them. A .NET runtime or SDK update does not establish that Aspire CLI was updated.

Have the runner owner verify the selected executable and resolved package pair before closing this maintenance item.

Use one acceptance record per runner

Agree four evidence fields: tool identity, security-package result, repetition of the original build command and client-integration acceptance. For example, a repaired CLI/SDK mismatch does not close the security row when the platform package is still unknown. A corrected package pair does not close a broken generated client.

Keep the release or image identifier with the record so a different runner image cannot silently inherit the conclusion. Unknown installation evidence should remain an open inventory question.

Decide who owns the next action

The agency owns the client-facing scope; the runner maintainer owns the tool installation and isolation boundary; the application team owns generated-client compatibility. Agree whether the next step is a tool update, a configuration correction or a bounded reproduction for upstream support. Skepra published this guide on 11 November 2026.

No real runner, client workload or exploit was tested for this article; the worksheet is a proposed handoff method.