From ecf0ceec163d746587955f1f23d0e721784fa54e Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Wed, 2 Sep 2026 01:20:27 +0000 Subject: [PATCH 1/2] docs: document VS Code outdated Aspire CLI warning Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../src/content/docs/get-started/aspire-vscode-extension.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx index 41d941a41..25581b62b 100644 --- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx +++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx @@ -67,6 +67,10 @@ The Command Palette has commands for the most common tasks: - **Aspire: Open Aspire terminal** drops you into a terminal with the Aspire CLI already on `PATH` for anything the UI doesn't cover. - **Aspire: Update Aspire CLI** and **Aspire: Install Aspire CLI** let you manage CLI installation. **Install Aspire CLI** shows a package-manager picker (WinGet, Homebrew, npm, .NET tool, or mise, depending on your platform) plus a **Daily build (dev)** option and a link to the full [installation guide](/get-started/install-cli/) for every option, including the install script. +:::note[Outdated CLI warning] +When an Aspire CLI operation such as a run/debug launch, a terminal command, or an `Aspire: ...` command uses a CLI executable that's outdated for its installed release lane (for example, an older `13.4.0` stable CLI when `13.5.2` stable is available), VS Code shows a warning notification identifying the exact executable. Choose **Update Aspire CLI** to update that resolved path, or **Don't Show Again** to suppress the warning for that exact path and version going forward. The check only compares within the same lane — a stable CLI is only compared against stable releases, and a daily/staging CLI only against prerelease releases — so it stays silent for local, PR, or unknown builds. +::: + ## Live editor integration When an AppHost is running, the extension paints live state directly into your editor. From f9001fe0f096f5b4f6aea54bfd6bf9c5f3259ed0 Mon Sep 17 00:00:00 2001 From: Ella Hathaway <67609881+ellahathaway@users.noreply.github.com> Date: Wed, 2 Sep 2026 13:14:04 -0700 Subject: [PATCH 2/2] Update outdated CLI warning explanation Clarified the outdated CLI warning section for better understanding. --- .../src/content/docs/get-started/aspire-vscode-extension.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx index 25581b62b..f678ca926 100644 --- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx +++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx @@ -68,7 +68,7 @@ The Command Palette has commands for the most common tasks: - **Aspire: Update Aspire CLI** and **Aspire: Install Aspire CLI** let you manage CLI installation. **Install Aspire CLI** shows a package-manager picker (WinGet, Homebrew, npm, .NET tool, or mise, depending on your platform) plus a **Daily build (dev)** option and a link to the full [installation guide](/get-started/install-cli/) for every option, including the install script. :::note[Outdated CLI warning] -When an Aspire CLI operation such as a run/debug launch, a terminal command, or an `Aspire: ...` command uses a CLI executable that's outdated for its installed release lane (for example, an older `13.4.0` stable CLI when `13.5.2` stable is available), VS Code shows a warning notification identifying the exact executable. Choose **Update Aspire CLI** to update that resolved path, or **Don't Show Again** to suppress the warning for that exact path and version going forward. The check only compares within the same lane — a stable CLI is only compared against stable releases, and a daily/staging CLI only against prerelease releases — so it stays silent for local, PR, or unknown builds. +VS Code shows a warning when it uses an Aspire CLI executable that is outdated within its release channel. This can happen when you run or debug an app, use the Aspire terminal, or run an Aspire: ... command. For example, VS Code might warn when it finds stable CLI 13.4.0 while stable 13.5.2 is available. Choose `Update Aspire CLI` to update the CLI or `Don't Show Again` to suppress warnings. ::: ## Live editor integration