Repository navigation
[docs] aspire update: show restore diagnostics on failure - #2186
Open
aspire-repo-bot[bot] wants to merge 2 commits into
Open
aspire-repo-bot[bot] wants to merge 2 commits into
aspire-repo-bot[bot] wants to merge 2 commits into
Conversation
4 of 14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
Maddy Montaquila (maddymontaquila)
marked this pull request as ready for review
November 17, 2026 19:01
Maddy Montaquila (maddymontaquila)
requested a review
from David Pine (IEvangelist)
as a code owner
November 17, 2026 19:01
Maddy Montaquila (maddymontaquila)
approved these changes
Nov 17, 2026
Maddy Montaquila (maddymontaquila)
enabled auto-merge (squash)
November 17, 2026 19:01
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The documentation promises restore diagnostics in 17.0, but that release branch still reports only a generic failure; the new behavior is targeted for 17.1.
1 open issue
What changed in this PR
Updates the aspire update CLI reference to describe restore-failure diagnostics introduced by microsoft/aspire#22355.
Changes:
- Revises the existing bullet to state that package updates are followed by a single restore and that failed restore output is displayed.
- Removes the previous explanation about avoiding mid-update failures during channel switches.
| File | Description |
|---|---|
src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx |
Updates the restore behavior description to mention failure output. |
Review effort: Balanced
| - Respects your configured Aspire channel (preview, stable, etc.) | ||
| - Resolves diamond dependencies to avoid duplicate updates | ||
| - Applies all package version edits before running a single final `dotnet restore`, so channel switches that add NuGet source mappings don't cause restore failures mid-update | ||
| - Applies all package updates, then runs a single `dotnet restore`, and shows the restore output if it fails |
Maddy Montaquila (maddymontaquila)
disabled auto-merge
November 17, 2026 19:15
Maddy Montaquila (maddymontaquila)
changed the base branch from
release/17.0
to
main
November 17, 2026 19:15
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Maddy Montaquila (maddymontaquila)
force-pushed
the
docs/pr-22355-43996998594-1-2d851daceb18004c
branch
from
November 17, 2026 19:28
e9cade9 to
021e8b5
Compare
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.

Documents changes from microsoft/aspire#22355
Author:
@JamesNKTargeting
release/17.0, the latest release branch onmicrosoft/aspire.dev, because the source PR has no milestone orrelease/*base ref to derive a more specific target (candidate_source:fallback_main,target_resolution:latest_release_fallback).Why:
aspire updatenow capturesdotnet restorestdout/stderr in the CLI log and displays it when the final restore fails (e.g. access denied on a locked task assembly). Triggered signals:pr_body_has_cli_flag_mention,pr_body_has_user_facing_section.Changes (updated page):
src/frontend/src/content/docs/reference/cli/commands/aspire-update.mdx: added a bullet describing the restore-failure output.