From 4c02f6f3f678d2b367985b7a2c0ad2a7a25064c3 Mon Sep 17 00:00:00 2001
From: "aspire-repo-bot[bot]"
 <268009190+aspire-repo-bot[bot]@users.noreply.github.com>
Date: Mon, 17 Aug 2026 02:54:07 +0000
Subject: [PATCH 1/2] docs: document mixed-quality staging package discovery
 for aspire add

Documents microsoft/aspire#19426 - Fix mixed-quality staging package discovery.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 .../content/docs/reference/cli/commands/aspire-add.mdx | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx
index 54a47daf5..03afce1ff 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx
@@ -26,6 +26,10 @@ The `aspire add` command searches for an integration package and adds it to the
 
 <Include relativePath="reference/cli/includes/project-search-logic-description.md" />
 
+:::note[Integration discovery on prerelease CLI builds]
+When you're running a `staging` or `dev` quality CLI (see [`-Quality|--quality`](/reference/cli/install-script/#options)), `aspire add` discovers both stable and prerelease integration packages, because some integrations — such as `Aspire.Hosting.Azure.Kubernetes` — intentionally ship as prerelease even during a stable-shaped staging build. A `release` quality CLI continues to search stable packages only, but can still add a specific prerelease integration version with the `-v, --version` option.
+:::
+
 ## Arguments
 
 The following arguments are available:
@@ -81,3 +85,9 @@ The following options are available:
   ```bash title="Aspire CLI"
   aspire add redis --apphost './apphost.mts'
   ```
+
+- Add the **azure-kubernetes** integration from a stable-shaped `staging` quality CLI, where the integration remains prerelease even though most other packages are stable:
+
+  ```bash title="Aspire CLI"
+  aspire add azure-kubernetes
+  ```

From 72d23eddd5b3741618d2a781a19eefeea5917df5 Mon Sep 17 00:00:00 2001
From: David Pine <david.pine@microsoft.com>
Date: Tue, 18 Aug 2026 09:09:52 -0500
Subject: [PATCH 2/2] Apply suggestions from code review

Co-authored-by: David Pine <david.pine@microsoft.com>
---
 .../src/content/docs/reference/cli/commands/aspire-add.mdx      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx
index 03afce1ff..6a5e45169 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-add.mdx
@@ -27,7 +27,7 @@ The `aspire add` command searches for an integration package and adds it to the
 <Include relativePath="reference/cli/includes/project-search-logic-description.md" />
 
 :::note[Integration discovery on prerelease CLI builds]
-When you're running a `staging` or `dev` quality CLI (see [`-Quality|--quality`](/reference/cli/install-script/#options)), `aspire add` discovers both stable and prerelease integration packages, because some integrations — such as `Aspire.Hosting.Azure.Kubernetes` — intentionally ship as prerelease even during a stable-shaped staging build. A `release` quality CLI continues to search stable packages only, but can still add a specific prerelease integration version with the `-v, --version` option.
+When you're running a `staging` or `dev` quality CLI (see [`-Quality|--quality`](/reference/cli/install-script/#options)), `aspire add` discovers both stable and prerelease integration packages, because some integrations — such as `Aspire.Hosting.Azure.Kubernetes` — intentionally ship as prerelease even during a stable-shaped staging build. A `release` quality CLI continues to search stable packages only, but can still add a specific prerelease integration version with the `--version` option.
 :::
 
 ## Arguments