Skip to content

[docs] What's new in Aspire 13.5 — VS Code extension v1.14.0#1223

Closed
aspire-repo-bot[bot] wants to merge 1 commit into
release/13.5from
docs/aspire-13-5-vscode-extension-release-44ee09131f38009a
Closed

[docs] What's new in Aspire 13.5 — VS Code extension v1.14.0#1223
aspire-repo-bot[bot] wants to merge 1 commit into
release/13.5from
docs/aspire-13-5-vscode-extension-release-44ee09131f38009a

Conversation

@aspire-repo-bot

Copy link
Copy Markdown
Contributor

Documents changes from microsoft/aspire#17969 (@aspire-repo-bot, merged by @adamint).

Targeting release/13.5 based on the source PR milestone 13.5 (exact match on microsoft/aspire.dev).

Why this PR is needed

The VS Code extension release preparation PR (microsoft/aspire#17969) bumped the extension to v1.14.0 and added a user-facing CHANGELOG entry covering new features, security hardening, and a security-advisory dependency update. The pr_body_has_security_marker signal fired because the PR body explicitly lists a [security] bullet for npm dependency updates. The "What's new in Aspire 13.5" page did not exist yet on the release/13.5 branch.

What was changed

  • Created src/frontend/src/content/docs/whats-new/aspire-13-5.mdx — new What's New page documenting:

    • Bun debugging support for Bun services running under Aspire
    • Improved parameter display (secrets masked, long values truncated, missing values shown explicitly)
    • Shell injection hardening via structured shell quoting for Aspire CLI arguments
    • npm security dependency updates (undici, ws, fast-uri, qs, @nevware21/ts-utils)
    • AppHost discovery flood fix
    • Compatibility error display when AppHost returns empty describe output
  • Modified src/frontend/config/sidebar/docs.topics.ts — added Aspire 13.5 entry before Aspire 13.4 in the What's new sidebar section.

Files

File Action
src/frontend/src/content/docs/whats-new/aspire-13-5.mdx Created
src/frontend/config/sidebar/docs.topics.ts Updated

Generated by PR Documentation Check for issue #17969 · sonnet46 4.9M ·

Documents the VS Code extension v1.14.0 release shipped with Aspire 13.5:
- Bun debugging support for Bun services
- Improved parameter display (secrets masked, long values truncated,
  missing values shown explicitly)
- Shell injection hardening via structured shell quoting
- npm security dependency updates (undici, ws, fast-uri, qs,
  @nevware21/ts-utils)
- AppHost discovery flood fix
- Compatibility error display for empty describe output

Also adds the Aspire 13.5 entry to the What's new sidebar.

Closes microsoft/aspire#17969

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@aspire-repo-bot aspire-repo-bot Bot added the docs-from-code Copilot initiated issue from dotnet/aspire repo label Jun 6, 2026
@aspire-repo-bot aspire-repo-bot Bot requested a review from adamint June 6, 2026 05:32
@aspire-repo-bot

Copy link
Copy Markdown
Contributor Author

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1223. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

VS Code: Open PR #1223 artifacts

This comment updates automatically when a new frontend build artifact is uploaded.

@IEvangelist IEvangelist marked this pull request as ready for review June 6, 2026 05:53
@IEvangelist IEvangelist self-requested a review as a code owner June 6, 2026 05:53
Copilot AI review requested due to automatic review settings June 6, 2026 05:53

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Adds the Aspire 13.5 “What’s new” documentation page (focused on VS Code extension v1.14.0 changes) and wires it into the docs sidebar navigation so it appears in the “What’s new” section.

Changes:

  • Created a new Aspire 13.5 release notes page covering VS Code extension improvements and security-related dependency updates.
  • Updated the docs sidebar to include the new Aspire 13.5 entry ahead of 13.4.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
src/frontend/src/content/docs/whats-new/aspire-13-5.mdx New “What’s new in Aspire 13.5” page documenting VS Code extension v1.14.0 updates and fixes.
src/frontend/config/sidebar/docs.topics.ts Adds the Aspire 13.5 page to the “What’s new” sidebar list.

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

Comment on lines +12 to +15
import {
Aside,
Icon,
} from '@astrojs/starlight/components';

@IEvangelist IEvangelist left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

[automated docs-from-code review]

I tried to verify this PR's claims against microsoft/aspire, but there is no matching release/13.5 branch in microsoft/aspire yet.

  • This PR targets release/13.5 in microsoft/aspire.dev.
  • The latest release/* branch in microsoft/aspire is release/13.4 (HEAD 4f2189335Fix persistent container endpoint allocation (#17960), 2026-06-05).
  • The source PR (microsoft/aspire#17969) merged into main, not into a release/13.5 branch.

My review protocol uses the matching release branch as the only source of truth, and I'm not allowed to verify a release/13.5 docs page against main (which can drift from what eventually ships in 13.5). I'll re-run automatically once release/13.5 is cut in microsoft/aspire, at which point I can verify each VS Code extension v1.14.0 claim against the actual snapshot.

Skipping Phase B (doc-tester) as well, per the same rule.

branch-mismatch — no verification or doc-tester run performed

@adamint adamint closed this Jun 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-from-code Copilot initiated issue from dotnet/aspire repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants