Skip to content

[docs] aspire update: show restore diagnostics on failure - #2186

Open
aspire-repo-bot[bot] wants to merge 2 commits into
mainfrom
docs/pr-22355-43996998594-1-2d851daceb18004c
Open

aspire-repo-bot[bot] wants to merge 2 commits into
mainfrom
docs/pr-22355-43996998594-1-2d851daceb18004c

Conversation

@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Documents changes from microsoft/aspire#22355

Author: @JamesNK

Targeting release/17.0, the latest release branch on microsoft/aspire.dev, because the source PR has no milestone or release/* base ref to derive a more specific target (candidate_source: fallback_main, target_resolution: latest_release_fallback).

Why: aspire update now captures dotnet restore stdout/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.

Generated by PR Documentation Check for #22355 · copilot · auto · 24.4 AIC · ⌖ 1.16 AIC · ⊞ 7.4K · ◷

@aspire-repo-bot aspire-repo-bot Bot added the docs-from-code Copilot initiated issue from dotnet/aspire repo label Nov 17, 2026
@aspire-repo-bot

Copy link
Copy Markdown
Contributor Author

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #2186. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

VS Code: Open PR #2186 artifacts

This comment updates automatically when a new frontend build artifact is uploaded.

@maddymontaquila
Maddy Montaquila (maddymontaquila) marked this pull request as ready for review November 17, 2026 19:01
Copilot AI balanced review requested due to automatic review settings November 17, 2026 19:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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
aspire-repo-bot Bot and others added 2 commits November 17, 2026 14:27
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@maddymontaquila
Maddy Montaquila (maddymontaquila) force-pushed the docs/pr-22355-43996998594-1-2d851daceb18004c branch from e9cade9 to 021e8b5 Compare November 17, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-from-code Copilot initiated issue from dotnet/aspire repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants