Skip to content

[docs] Document Aspire skills bundle fallback in aspire agent init#1094

Open
aspire-repo-bot[bot] wants to merge 1 commit into
release/13.4from
docs/aspire-skills-bundle-fallback-17537-cbbfde360ada8d15
Open

[docs] Document Aspire skills bundle fallback in aspire agent init#1094
aspire-repo-bot[bot] wants to merge 1 commit into
release/13.4from
docs/aspire-skills-bundle-fallback-17537-cbbfde360ada8d15

Conversation

@aspire-repo-bot
Copy link
Copy Markdown
Contributor

Documents changes from microsoft/aspire#17537 by @IEvangelist.

Targeting release/13.4 — the latest release branch on microsoft/aspire.dev — because release/13.5 (from the source PR milestone 13.5) does not exist there.

Why this PR is needed

PR microsoft/aspire#17537 changed aspire agent init (and the chained aspire new/aspire init flow) to use best-effort behavior when acquiring the Aspire skills bundle. Instead of failing with a non-zero exit code when the GitHub release asset is unavailable, the command now falls back to an embedded snapshot and, if that also fails, warns and skips only the bundle-backed skills. The existing docs described the command as always downloading skills from GitHub, leaving users in restricted-network or air-gapped environments without guidance.

Changes made

Updated src/frontend/src/content/docs/reference/cli/commands/aspire-agent-init.mdx:

  • Added a new "Aspire skills bundle acquisition" subsection under the Description that explains the three-level resolution order:
    1. Existing validated cache
    2. GitHub release asset (with artifact attestation verification)
    3. Embedded CLI snapshot (offline/air-gapped fallback)
  • Documented the best-effort behavior: when all sources fail the command warns and skips bundle-backed skills rather than exiting non-zero.
  • Noted that aspire new and aspire init chained flows follow the same behavior.

Generated by PR Documentation Check for issue #17537 · ● 9.8M ·

… init

Document the best-effort skills bundle acquisition order (cache →
GitHub release asset → embedded snapshot) introduced in
microsoft/aspire#17537. The command now warns and skips bundle-backed
skills instead of failing when all acquisition sources are unavailable.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@aspire-repo-bot aspire-repo-bot Bot requested a review from mitchdenny May 27, 2026 15:19
@IEvangelist IEvangelist marked this pull request as ready for review May 31, 2026 04:38
@IEvangelist IEvangelist self-requested a review as a code owner May 31, 2026 04:38
Copilot AI review requested due to automatic review settings May 31, 2026 04:38
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Aspire CLI docs to reflect the new best-effort behavior of aspire agent init when acquiring the Aspire skills bundle, including offline/air-gapped fallback behavior introduced in microsoft/aspire#17537.

Changes:

  • Added a new “Aspire skills bundle acquisition” subsection describing the bundle resolution order (cache → GitHub release asset → embedded snapshot).
  • Documented best-effort behavior when all sources fail (warn + skip only bundle-backed skills), including parity for aspire new/aspire init chained flows.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


### Aspire skills bundle acquisition

When installing the Aspire skill, the command resolves the skills bundle using the following priority order:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant