From f6a71212530e21ec788b95480de7fa7a681da8cf Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Mon, 2 Nov 2026 10:06:11 +0000 Subject: [PATCH 1/2] Document aspire update --config-source project-local behavior Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../content/docs/reference/cli/commands/aspire-update.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx index 9073747930..157b61b6ba 100644 --- a/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx +++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx @@ -114,6 +114,14 @@ The following options are available: The `staging` channel can only be resolved from a `stable` or `staging` Aspire CLI build. Daily, local, and per-PR CLI builds don't have a deterministic staging feed, so requesting `--channel staging` from one of them fails with an error naming the running CLI's identity and pointing at the recovery options: install a staging or stable Aspire CLI, or set the `overrideStagingFeed` configuration value (for example, `aspire config set -g overrideStagingFeed `) to point at the staging feed you want to use. See [`overrideStagingFeed`](/reference/cli/configuration/#settings-surfaced-by-aspire-config) in the CLI configuration reference. +- **`--config-source`** + + Apply allowed settings from the nearest local saved Git configuration source, replacing local edits to supplied settings, without updating packages or the CLI. Configuration sources belong to projects: only the `configSource` binding in the selected project's nearest local `aspire.config.json` is checked and refreshed. Bindings in global configuration are ignored, so adding one has no effect. If only global configuration contains a binding, the command succeeds with the no-source notice and performs no Git acquisition or configuration writes. + + ```bash title="Aspire CLI" + aspire update --config-source --yes --non-interactive + ``` + - **`-y, --yes`** Automatically confirm all prompts without user input. Use this option in CI/CD pipelines or other non-interactive environments to skip confirmation dialogs. From b6e0f006e4eea33dbc03819b42e5f580bde4399c Mon Sep 17 00:00:00 2001 From: James Newton-King Date: Fri, 13 Nov 2026 13:49:54 +0800 Subject: [PATCH 2/2] Apply suggestion from @JamesNK --- .../src/content/docs/reference/cli/commands/aspire-update.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx index 157b61b6ba..ffbe1003d8 100644 --- a/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx +++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx @@ -116,7 +116,7 @@ The following options are available: - **`--config-source`** - Apply allowed settings from the nearest local saved Git configuration source, replacing local edits to supplied settings, without updating packages or the CLI. Configuration sources belong to projects: only the `configSource` binding in the selected project's nearest local `aspire.config.json` is checked and refreshed. Bindings in global configuration are ignored, so adding one has no effect. If only global configuration contains a binding, the command succeeds with the no-source notice and performs no Git acquisition or configuration writes. + Apply allowed settings from the nearest local saved Git configuration source, replacing local edits to supplied settings, without updating packages or the CLI. ```bash title="Aspire CLI" aspire update --config-source --yes --non-interactive