Repository navigation
[docs] Note ASPIREPIPELINES004 graduation in Aspire 17.0 - #1852
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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. |
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#20814
@mitchdennyTarget branch: Targeting
release/17.0based on the source PR milestone17.0(exact match found onmicrosoft/aspire.dev).Why this PR is needed
microsoft/aspire#20814 graduates the pipeline output-directory API family (
IPipelineOutputServiceandPipelineOutputService) from experimental to stable, removing theASPIREPIPELINES004experimental 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:The
ASPIREPIPELINES004diagnostic 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 inaspirepipelines001.mdx,aspireazure002.mdx, andaspirecosmosdb001.mdx) stating that as of Aspire 17.0,IPipelineOutputServiceandPipelineOutputServiceare no longer experimental and don't triggerASPIREPIPELINES004, and that the diagnostic only applies to earlier versions.No other pages reference
IPipelineOutputService/GetOutputDirectory/GetTempDirectoryby 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
src/frontend/src/content/docs/diagnostics/aspirepipelines004.mdxNo new pages were created.