Skip to content

[docs] Document in-process NuGet operations and credential provider support - #1731

Open
aspire-repo-bot[bot] wants to merge 1 commit into
release/13.6from
docs/pr-19847-35894452444-1-4b11b2810ef5cfd8
Open

aspire-repo-bot[bot] wants to merge 1 commit into
release/13.6from
docs/pr-19847-35894452444-1-4b11b2810ef5cfd8

Conversation

@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Documents changes from microsoft/aspire#19847.

@eerhardt

Target: release/13.6, based on the source PR milestone 13.6 (exact match: release/13.6 already exists on microsoft/aspire.dev).

Why

Source PR microsoft/aspire#19847 moves bundled Aspire CLI NuGet operations (search, restore, package probe-manifest generation) from a separate aspire-managed nuget subprocess into the Native AOT aspire executable, calling NuGet.Client APIs in-process. This is a user-facing change:

  • It removes a process hop for bundled NuGet operations (existing commands like aspire integration list and aspire add keep working without starting aspire-managed).
  • It's an intentional behavior change: the previous aspire-managed helper never initialized NuGet's credential service, so bundled search/restore could only use credentials stored in nuget.config. Feeds that rely on a credential provider plugin (for example, Azure Artifacts) returned 401. The in-process client now initializes the credential service, so installed credential provider plugins are used.

The PR body's "User-facing usage" and "Intentional behavior change: NuGet credential providers" sections both describe user-visible effects, which triggered the pr_body_has_user_facing_section and pr_body_has_cli_flag_mention signals (the latter from the --nuget-config fallback discussion). No existing docs mentioned this fix by name, so this PR documents it.

What changed

  • src/frontend/src/content/docs/whats-new/aspire-13-6.mdx: added a new "In-process NuGet operations, with credential provider support" subsection under "🛠️ Aspire CLI enhancements", explaining the removal of the aspire-managed subprocess hop for NuGet operations and the credential provider plugin fix. Also updated the release summary bullet to mention it.
  • src/frontend/src/content/docs/get-started/troubleshooting.mdx: added a note to the existing "aspire add finds no packages with an Azure Artifacts feed" troubleshooting entry, clarifying that 13.6+ initializes the NuGet credential service and how to further diagnose a persistent 401 after updating.

Both are updates to existing pages — no new pages were created.

Generated by PR Documentation Check for #19847 · copilot · auto · 117.5 AIC · ⌖ 17.6 AIC · ⊞ 18.7K · ◷

…(aspire#19847)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@aspire-repo-bot aspire-repo-bot Bot added the docs-from-code Copilot initiated issue from dotnet/aspire repo label Sep 23, 2026
Comment on lines +183 to +192
<Aside type="note">
Aspire 13.6 and later run bundled NuGet search and restore in-process
instead of through a separate `aspire-managed` helper, and initialize
NuGet's credential service so installed credential provider plugins are
used. If a feed still returns `401` after updating, confirm the
credential provider plugin (for example, the Azure Artifacts Credential
Provider) is installed and can authenticate outside Aspire, such as with
`dotnet nuget locals`.
</Aside>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is

Suggested change
<Aside type="note">
Aspire 13.6 and later run bundled NuGet search and restore in-process
instead of through a separate `aspire-managed` helper, and initialize
NuGet's credential service so installed credential provider plugins are
used. If a feed still returns `401` after updating, confirm the
credential provider plugin (for example, the Azure Artifacts Credential
Provider) is installed and can authenticate outside Aspire, such as with
`dotnet nuget locals`.
</Aside>

@eerhardt

Copy link
Copy Markdown
Member

This is unnecessary - no user facing change here.

@aspire-repo-bot

Copy link
Copy Markdown
Contributor Author

Frontend HTML artifact ready

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

VS Code: Open PR #1731 artifacts

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

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.

Copilot review overview

🟡 Changes recommended

Replace the dotnet nuget locals diagnostic with an operation that actually tests feed authentication.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1 Low severity

Open (1)
What changed in this PR

This docs-only PR documents Aspire 13.6’s in-process NuGet operations and credential-provider support.

Changes:

  • Adds release-note coverage for the CLI changes.
  • Updates Azure Artifacts troubleshooting guidance.
File Description
src/​frontend/​src/​content/​docs/​whats-new/​aspire-13-6.mdx Documents in-process NuGet behavior and credential providers.
src/​frontend/​src/​content/​docs/​get-started/​troubleshooting.mdx Adds Azure Artifacts troubleshooting guidance.

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +187 to +190
used. If a feed still returns `401` after updating, confirm the
credential provider plugin (for example, the Azure Artifacts Credential
Provider) is installed and can authenticate outside Aspire, such as with
`dotnet nuget locals`.
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.

3 participants