Repository navigation
docs: add prerelease (staging) testing walkthrough to upgrade guide - #2182
Merged
Merged
Conversation
Fixes #2181 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Maddy Montaquila (maddymontaquila)
requested a review
from David Pine (IEvangelist)
as a code owner
November 16, 2026 21:13
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The upgrade guide still gives misleading staging-update and NuGet configuration guidance across installation types and AppHost languages, and its diagnostics link lacks the highlighted warning’s migration instructions.
4 open issues
What changed in this PR
Adds a prerelease-testing walkthrough to the existing Aspire upgrade guide, bringing previously scattered staging guidance into one place.
Changes:
- Covers switching the CLI and app to staging and checking updater changes.
- Explains prerelease documentation configuration and verification.
- Lists settings to check manually and steps for returning to stable.
| File | Description |
|---|---|
src/frontend/src/content/docs/whats-new/upgrade-aspire.mdx |
Adds the six-step prerelease testing walkthrough. |
Review effort: Balanced
Contributor
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
…guage Address review feedback: npm/.NET tool CLIs don't switch channels via --self, C# AppHosts follow NuGet policy without --channel, NuGet side effects are C#-only and conditional, and link ASPIRE012 help directly. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
David Pine (IEvangelist)
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Adds a Try a prerelease build section to the upgrade guide. It walks through testing an app against a staging build from start to finish. Each piece was already documented on a different page, so the section links back to those references:
aspire update --self --channel staging; in CI, use install-script--quality staging.aspire update --channel staging --migrate. The section explains what this writes: thechannelentry inaspire.config.json, theNuGet.configstaging feed andAspire*source mapping, and the repo-local.nugetpackagesfolder to add to.gitignore. It also notes that--migratedoesn't apply approval-gated changes such as ASPIRE012.aspire docsat the prerelease docs (aka.ms/aspire/vnext) by setting bothdocs.llmsTxtUrlanddocs.api.sitemapUrl.NuGet.configentries thataspire updatecan leave behind.Each step reflects what happened when maddymontaquila/aspirifridays was upgraded from 13.5.3 to 17.0 staging.
The section uses a
<prerelease-host>placeholder because theaka.ms/aspire/vnextlink doesn't pass paths through; for example,/llms-full.txtredirects to Bing.Fixes #2181. Related: #2133, #2177, #1880, #2180, and microsoft/aspire#22335.
Third-party links and affiliations
None
Validation
aspire.config.jsoncontained"channel": "staging".NuGet.confighad the darc feed, theAspire*mapping, andglobalPackagesFolder=.nugetpackages.release/17.0. CI covers the build and link checks.