From d184e21ed4d94d8f1e0510fafd6315acd0e19d9f Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Thu, 12 Nov 2026 18:54:59 +0000 Subject: [PATCH] Document configured channel for aspire update --- .../src/content/docs/reference/cli/commands/aspire-update.mdx | 2 ++ 1 file changed, 2 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..6ab78c1079 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 @@ -108,6 +108,8 @@ The following options are available: Channel to update to (`stable`, `staging`, `daily`). When switching channels, `aspire update` applies all package version edits to your project first and then runs a single `dotnet restore`, ensuring that NuGet source mappings added for the target channel are in place before any restore is attempted. + When you don't pass `--channel` (or the legacy `--quality` option), `aspire update` uses the `channel` value from your Aspire configuration, for C# AppHosts as well as guest AppHosts. The configuration lookup uses the nearest project settings (`aspire.config.json` or legacy settings) and then falls back to the global configuration. A configured channel goes through the same NuGet policy comparison, preview, approval, validation, and rejection rules as `--channel`. For a non-stable configured channel, the command reports `Using channel 'daily' from Aspire configuration. Pass --channel to override.`; a configured `stable` channel applies the normal stable-channel cleanup without that message. An unknown or unavailable configured channel fails with an error that identifies the configuration as the source instead of silently falling back. When neither `--channel` nor a configured channel is present, C# AppHosts keep the existing NuGet policy. + For non-stable channels (`staging`, `daily`), `aspire update` creates or updates a project-level `nuget.config` with the source mappings needed to resolve packages from that channel's feed. For the `stable` channel, no `nuget.config` is created because nuget.org is already the default NuGet source. If an existing `nuget.config` is present and the project has package or channel updates to apply when switching to or using `stable`, those changes are applied as part of that update to remove any stale channel-specific feed entries. If the project is already up to date, `aspire update` reports this and exits before touching `nuget.config`, so a stale channel-specific feed entry from a previous `staging` or `daily` switch can remain until the next update that actually applies changes. When you switch to a persistable channel, such as `daily`, `aspire update` also rewrites the top-level `channel` key in `aspire.config.json` when the file already exists. Only channels registered as _explicit_ channels are persisted, with one exception: the `stable` channel is treated as the portable default and is intentionally not pinned. The persisted channel keeps subsequent `aspire add` and `aspire update` runs resolving packages against the channel you just switched to.