Skip to content

[docs] Note ASPIREPIPELINES004 graduation in Aspire 17.0 - #1852

Draft
aspire-repo-bot[bot] wants to merge 1 commit into
release/17.0from
docs/pr-20814-37860851693-1-fdcdea9682a3958b
Draft

aspire-repo-bot[bot] wants to merge 1 commit into
release/17.0from
docs/pr-20814-37860851693-1-fdcdea9682a3958b

Conversation

@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Documents changes from microsoft/aspire#20814

@mitchdenny

Target branch: Targeting release/17.0 based on the source PR milestone 17.0 (exact match found on microsoft/aspire.dev).

Why this PR is needed

microsoft/aspire#20814 graduates the pipeline output-directory API family (IPipelineOutputService and PipelineOutputService) from experimental to stable, removing the ASPIREPIPELINES004 experimental attribute and all suppressions for it across hosting, Azure deployment infrastructure, EF Core, Radius, and the linked publishing helper. The source PR's own description states:

User-facing usage

Given an IPipelineOutputService outputService and an IResource resource, the existing calls no longer require an ASPIREPIPELINES004 suppression:

var outputDirectory = outputService.GetOutputDirectory();
var resourceOutputDirectory = outputService.GetOutputDirectory(resource);
var tempDirectory = outputService.GetTempDirectory();
var resourceTempDirectory = outputService.GetTempDirectory(resource);

The ASPIREPIPELINES004 diagnostic page previously described these APIs as experimental with no indication that they later graduated. This left a documentation gap for anyone encountering the diagnostic page via search after upgrading to 17.0 and no longer seeing the warning.

What changed

  • src/frontend/src/content/docs/diagnostics/aspirepipelines004.mdx: Added an <Aside type="note"> (matching the established pattern used in aspirepipelines001.mdx, aspireazure002.mdx, and aspirecosmosdb001.mdx) stating that as of Aspire 17.0, IPipelineOutputService and PipelineOutputService are no longer experimental and don't trigger ASPIREPIPELINES004, and that the diagnostic only applies to earlier versions.

No other pages reference IPipelineOutputService/GetOutputDirectory/GetTempDirectory by name, and the diagnostics overview table's one-line description is left unchanged (consistent with how other graduated diagnostics — e.g. ASPIREAZURE002 — are still listed there verbatim).

Pages updated

  • Updated: src/frontend/src/content/docs/diagnostics/aspirepipelines004.mdx

No new pages were created.

Generated by PR Documentation Check for #20814 · copilot · auto · 54.3 AIC · ⌖ 10.6 AIC · ⊞ 20.4K · ◷

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 Oct 8, 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 #1852. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

VS Code: Open PR #1852 artifacts

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

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.

0 participants