Skip to content

Add a walkthrough for testing apps against Aspire prerelease (staging) builds #2181

Closed

Description

Summary

There's no single page on testing an app against an Aspire prerelease (staging/daily) build. Each piece is documented somewhere, but someone has to assemble them by hand. I hit this upgrading maddymontaquila/aspirifridays from 13.5.3 to 17.0 staging, and ended up reading CLI source to find the docs-override keys before I found them in the configuration reference.

The upgrade guide and What's new in 17 cover only the stable path.

Suggested walkthrough (one page or an upgrade-guide section)

  1. Update the CLI: aspire update --self --channel staging (and the equivalent install.sh --quality staging for CI).

  2. Update the app: aspire update --channel staging --migrate. Explain what it writes:

  3. Point docs at the matching prerelease site so aspire docs and agent skills read vnext content. Set both keys:

    • docs.llmsTxtUrl → <vnext>/llms-full.txt
    • docs.api.sitemapUrl → <vnext>/sitemap-0.xml

    Mention that aka.ms/aspire/vnext resolves to the vnext host, and that its sitemap still lists canonical aspire.dev URLs.

  4. Verify: aspire --version, check package versions, and confirm aspire docs search hits vnext-only content.

  5. Watch for leftovers the updater doesn't touch: inactive central package pins, other AppHosts in the repo, and pinned CI installers.

  6. Switch back to stable when done.

Related

Activity

  1. added a commit that references this issue on Nov 17, 2026
    3755a97
  2. maddymontaquila commented on Nov 17, 2026

    @maddymontaquila
    ContributorAuthor

    Fixed by #2182 (merged to release/17.0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationmissing-conceptual-docsNew API/behavior shipped without conceptual documentation

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions