Prepare VS Code extension release v1.12.0#17801
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 17801Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 17801" |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Commit pushed:
|
|
Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
|
Trim leading blank lines when prepending the generated release entry so extension release PRs start with Markdownlint-clean changelogs, and remind the changelog agent to avoid MD012 output. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Prepares the Aspire VS Code extension for the v1.12.0 release by bumping the extension version, adding a v1.12.0 changelog entry, and tightening the extension release workflow’s changelog-merge behavior to avoid Markdownlint failures.
Changes:
- Bump extension version from 1.11.0 to 1.12.0.
- Add a v1.12.0 entry to
extension/CHANGELOG.md. - Update the extension release workflow to strip leading blank lines when appending the prior changelog body (avoids multiple consecutive blank lines).
Show a summary per file
| File | Description |
|---|---|
| extension/package.json | Bumps the extension version to 1.12.0. |
| extension/CHANGELOG.md | Adds the v1.12.0 release notes entry. |
| .github/workflows/extension-release.yml | Adjusts changelog update logic to avoid introducing extra blank lines. |
| .github/workflows/extension-changelog.md | Updates workflow guidance to explicitly avoid multiple consecutive blank lines (MD012). |
Copilot's findings
- Files reviewed: 4/4 changed files
- Comments generated: 1
|
|
||
| ### Features | ||
|
|
||
| - Add VS Code telemetry signals for engagement, AppHost launches, command invocations, debug sessions, and dashboard telemetry passthrough; all events respect the VS Code `telemetry.telemetryLevel` setting ([#17723](https://github.com/microsoft/aspire/pull/17723)). |
Link the tracking issue and implementation PR separately in the release note, and update the changelog agent prompt to preserve issue versus pull request references. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Clear the Aspire panel loading context when workspace AppHost discovery or workspace ps reaches a terminal state, and avoid rediscovery churn from .worktrees folders. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
❓ CLI E2E Tests unknown — 110 passed, 0 failed, 2 unknown (commit View all recordings
📹 Recordings uploaded automatically from CI run #26774676477 |
|
✅ No documentation update needed. docs_optional → internal_refactor No triggered signals (signal_count: 0). This is a VS Code extension release preparation PR (v1.12.0) that adds telemetry signals internal to the VS Code extension. The telemetry implementation follows VS Code's standard Changed files justify the category:
|
Brings 43 release-branch commits forward onto main now that 13.4.0 has shipped. This PR replaces the original automated merge (microsoft#17804) which had to be closed so that conflict resolution and post-merge cleanups could be made on a non-protected branch. Conflict resolution summary (33 files): * Equivalent backports (took main's commit identity): ChannelUpdateWorkflowTests, LoggingHelpersTests, the four extension test files, AspireEditorCommandProvider, appHostDiscovery. * Release-only forwards (preserved): microsoft#17732 / microsoft#17756 Foundry hosted-agent protocol selection and cross-compute-environment endpoint references, microsoft#17573 stabilize PrebuiltAppHostServer staging globalPackagesFolder path, microsoft#17743 staging-identity CLI darc feed routing. * Main-only forwards (preserved): microsoft#17506 Show discovered AppHosts in Aspire pane, microsoft#17547 Localize Aspire skills metadata errors, microsoft#17801 VS Code v1.12.0, microsoft#17297 Aspire CLI npm package release integration, microsoft#17576 TerminalRun IAsyncDisposable, microsoft#17721 / microsoft#17723 VS Code telemetry, microsoft#17671 ATS baseline fix (re-applied manually on top of Foundry source taken from release). * Hybrid (manually spliced): docs/contributing.md - kept main's restructured layout and inserted release's staging-validation paragraph; HostedAgentBuilder- Extension - took release base then re-applied microsoft#17671 asHostedAgent rename; UpdateCommandTests - took main and injected microsoft#17743's OverrideCliInformationalVersionConfigKey block. Post-merge cleanups included in this PR: * eng/Versions.props: revert StabilizePackageVersion to false (was flipped to true on release/13.4 by microsoft#17520 for shipping 13.4.0; main must stay in preview mode). * .github/workflows/generate-api-diffs.yml: retarget back to main (was pointed at release/13.4 by microsoft#17696 release prep). * .github/workflows/backmerge-release.yml: update from release/13.3 to release/13.4 (was stale - missed the 13.4 release-time bump). * .github/workflows/milestone-assignment.yml: audited - already correct (main -> 13.5, release/13.4 -> 13.4.x); no change. This merge commit must be preserved - do not squash on merge. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
VS Code Extension Release v1.12.0
Version bump: 1.11.0 → 1.12.0
Commit range:
01c5a9a..54ff1b9Baseline: VS Code Marketplace v1.11.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.