Repository navigation
[docs] Document graduation of user secrets manager APIs to stable - #1854
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
Document that IUserSecretsManager and IDistributedApplicationBuilder.UserSecretsManager have graduated from experimental to stable in Aspire 17.0, following microsoft/aspire#20817. - Update ASPIREUSERSECRETS001 diagnostic page to reflect the graduation, matching the pattern used for ASPIREACADOMAINS001. - Add a What's new in Aspire 17.0 entry announcing the graduation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
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#20817
@mitchdennyTarget branch
Targeting
release/17.0based on the source PR milestone17.0(exact match onmicrosoft/aspire.dev).Why this is needed
microsoft/aspire#20817 graduates the
ASPIREUSERSECRETS001API family (IUserSecretsManagerandIDistributedApplicationBuilder.UserSecretsManager) from experimental to stable, removing all experimental attributes and suppression directives. This is an attribute-only change — signatures, defaults, and behavior are unchanged.The PR body's "User-facing usage" section shows that existing code (
builder.UserSecretsManager) no longer needs anASPIREUSERSECRETS001suppression, which is a direct, user-visible documentation gap: the diagnostics page still described these APIs as experimental.What changed
src/frontend/src/content/docs/diagnostics/aspireusersecrets001.mdx(updated): Reworded the page to describeASPIREUSERSECRETS001as a pre-17.0 diagnostic, following the same pattern used forASPIREACADOMAINS001whenConfigureCustomDomaingraduated. Added a:::notecallout announcing the graduation, changed the example to "Before Aspire 17.0, the following code generated...", and updated "To correct this warning" to state that Aspire 17.0+ consumers don't need to suppress the diagnostic.src/frontend/src/content/docs/whats-new/aspire-17.mdx(updated): Added a new "🔐 User secrets manager APIs are stable" section before the breaking-changes section, with a short code sample and a cross-link back to the diagnostic page.No new pages were created; both existing pages were updated in place.
Validation
Documentation-only change; no test commands were run per the
pr-testingguidance for doc-only edits. Reviewed the edited files for Markdown formatting (no consecutive blank lines, fenced code blocks with language identifiers) and confirmed theseoTitlestays within the SEO length guard.