[docs] Use SHA-512 for Aspire Skills bundle integrity, hide remote-fetch toggle - #1485
Merged
David Pine (IEvangelist) merged 1 commit intoAug 13, 2026
Conversation
…oggle Documents changes from microsoft/aspire#19303: the Aspire Skills bundle full-file integrity checks now use SHA-512 (previously SHA-256), and the aspireSkillsRemoteFetchEnabled preview toggle is hidden from aspire config output and the generated VS Code settings schemas. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
David Pine (IEvangelist)
marked this pull request as ready for review
August 13, 2026 15:29
David Pine (IEvangelist)
requested review from
David Pine (IEvangelist) and
Mitch Denny (mitchdenny)
as code owners
August 13, 2026 15:29
David Pine (IEvangelist)
merged commit Aug 13, 2026
32f826f
into
release/13.5
10 of 11 checks passed
David Pine (IEvangelist)
deleted the
docs/pr-19303-31708507560-1-8825432ae7dccb19
branch
August 13, 2026 15:29
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Aspire CLI documentation to reflect upstream Aspire 13.6 behavioral changes: SHA-512-based Aspire Skills bundle integrity verification (with SHA-256 compatibility for older bundles) and the remote-fetch preview toggle becoming hidden from aspire config output / VS Code settings schemas.
Changes:
- Removes the hidden
features.aspireSkillsRemoteFetchEnabledentry from the CLI config settings reference table. - Adds a note that the remote-fetch setting is now hidden (but still works if set directly) and documents bundle integrity verification behavior.
- Updates the documented bundle-verification failure message to SHA-512 to match current CLI output.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/frontend/src/content/docs/reference/cli/includes/config-settings-table.md | Removes the now-hidden remote-fetch preview setting from the config settings table. |
| src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx | Documents the hidden toggle behavior and adds a bundle integrity verification section describing SHA-512 (+ SHA-256 legacy support). |
| src/frontend/src/content/docs/get-started/aspire-skills.mdx | Updates the embedded bundle verification error message to SHA-512. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+62
to
+65
| The `features.aspireSkillsRemoteFetchEnabled` setting is hidden from `aspire | ||
| config` output and the generated VS Code settings schemas as of Aspire | ||
| 13.6—it's still off by default and still works if you set it directly, | ||
| as shown above. |
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#19303
@IEvangelistTargeting
release/13.5— the latest release branch onmicrosoft/aspire.dev— becauserelease/13.6(from the source PR milestone13.6) does not exist there.Why
The source PR switches the Aspire Skills bundle full-file integrity check from SHA-256 to SHA-512 (aligning with the CLI acquisition scripts), and marks the
aspireSkillsRemoteFetchEnabledpreview feature flag as hidden — it no longer appears inaspire configoutput or the generated VS Code settings schemas, though the flag and its off-by-default value are unchanged and it still works if set directly.Triggered signals:
cli_command_file_changed(ConfigCommand.cs),cli_resource_strings_changed(AgentCommandStrings.resx).Documentation changes
src/frontend/src/content/docs/reference/cli/includes/config-settings-table.md— removed thefeatures.aspireSkillsRemoteFetchEnabledrow since it's now hidden fromaspire configoutput.src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx— added a note next to the existing remote-fetch example clarifying the setting is hidden as of Aspire 13.6 (still works if set directly), and a short "Bundle integrity verification" section describing the SHA-512 checksum (with SHA-256 fallback for pre-switch bundles).src/frontend/src/content/docs/get-started/aspire-skills.mdx— updated the embedded bundle verification failure error message from SHA-256 to SHA-512 to match the current CLI behavior.All edits update existing pages; no new pages were created.