Prepare VS Code extension release v1.14.0#17969
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 17969Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 17969" |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
There was a problem hiding this comment.
Pull request overview
Prepares the Aspire VS Code extension for the v1.14.0 Marketplace release by bumping the extension version and adding the corresponding changelog entry.
Changes:
- Bump VS Code extension version from
1.13.0to1.14.0inextension/package.json. - Add
v1.14.0release notes toextension/CHANGELOG.md(features + fixes list).
Show a summary per file
| File | Description |
|---|---|
| extension/package.json | Updates the extension’s published version to 1.14.0. |
| extension/CHANGELOG.md | Adds the v1.14.0 changelog entry covering the release’s user-facing changes. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 0
|
❓ CLI E2E Tests unknown — 113 passed, 0 failed, 2 unknown (commit View all recordings
📹 Recordings uploaded automatically from CI run #27052863313 |
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>
|
Pull request created: #1223
|
|
📝 Documentation has been drafted in microsoft/aspire.dev#1223 targeting Created a new What's new in Aspire 13.5 page documenting the VS Code extension v1.14.0 release. The Files changed:
Note This draft PR needs human review before merging. |
VS Code Extension Release v1.14.0
Version bump: 1.13.0 → 1.14.0
Commit range:
e20049f..bba091aBaseline: VS Code Marketplace v1.13.0 (from the shipped VSIX
extension/.version)Proposed release notes (deterministic fallback)
The
extension-changelogagentic workflow generates the final, polishedextension/CHANGELOG.mdentry and replaces the placeholder on this branch. The commit-derived list below is the human-reviewable fallback — if the agent does not run, paste it intoextension/CHANGELOG.mdbefore merging.Changes (auto-generated from commits)
Release instructions
Confirm
extension/CHANGELOG.mdis specific, user-facing, and free of internal-only changes. Theextension-changelogagentic workflow replaces the placeholder entry with generated notes shortly after this PR is opened; if the placeholder is still present, fill it in from the deterministic fallback above before merging.Get a signed Azure DevOps
microsoft-aspiresource build of the merge commit that published theaspire-vscode-extensionartifact with exactly one.vsix, matching.manifest, and matching.signature.p7s:microsoft-aspirepipeline on the merge commit withPackage VS Code Extension as Pre-Release=true, then use that build instead. The publish job fails if the VSIX pre-release flag does not matchIsPrerelease.Run Azure DevOps pipeline
release-publish-nugetand select that build under Resources →aspire-build.For an extension-only release, use these parameters:
ReleaseVersionautoIsPrereleasefalsefor a stable release,truefor a pre-releaseDryRunfalseSkipNuGetPublishtrueSkipChannelPromotiontrueSkipWinGetPublishtrueSkipHomebrewValidationtrueSkipGitHubTaskstrueSkipReleaseAssetstrueSkipVSCodeExtensionPublishfalseFor a full Aspire release, keep the normal NuGet/channel/GitHub task settings and additionally set
SkipVSCodeExtensionPublish=false. For a pre-release extension, also use a source build queued withPackage VS Code Extension as Pre-Release=trueand setIsPrerelease=true.To validate without publishing, run the same pipeline with
DryRun=trueandSkipVSCodeExtensionPublish=false; the release job validates the VSIX/manifest/signature triplet and Marketplace PAT but skipsvsce publish.