[release/13.4] Add Aspire CLI npm package release integration - #17733
Closed
Adam Ratzman (adamint) wants to merge 1 commit into
Closed
[release/13.4] Add Aspire CLI npm package release integration#17733Adam Ratzman (adamint) wants to merge 1 commit into
Adam Ratzman (adamint) wants to merge 1 commit into
Conversation
Backport of microsoft#17297 to release/13.4. Conflicts resolved in extension/Extension.proj, extension/build.ps1, and extension/build.sh by taking the PR's Corepack-based build flow, since the PR also adds the Corepack bootstrap infrastructure (install-corepack.yml, prepareCorepackYarn.mjs, corepack-version.txt) that release/13.4 lacked. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Adam Ratzman (adamint)
requested review from
James Newton-King (JamesNK),
David Fowler (davidfowl) and
Mitch Denny (mitchdenny)
as code owners
May 30, 2026 18:44
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 17733Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 17733" |
16 tasks
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #17297 to release/13.4
/cc Adam Ratzman (@adamint)
Customer Impact
Completes the production path for shipping the Aspire CLI through npm (
@microsoft/aspire-clipointer package plus the RID-specific packages like@microsoft/aspire-cli-linux-x64). Without it, 13.4 can't distribute the CLI to npm users, and anyone who did install via npm gets no upgrade guidance fromaspire update. It's a net-new distribution channel — nothing changes for users who get the CLI any other way.Testing
Built
Aspire.Cliagainst release/13.4 (clean) and ran the affected suites locally — 76 CLI tests (npm detection + update command) and 33 infra tests (npm package + release pipeline) all pass. The end-to-end ESRP/MicroBuild npm publish only runs at release time, so it hasn't been exercised from this branch.Risk
Medium. The runtime CLI change is small and well-tested (npm install detection + an update message). The bulk is release/packaging infra (AzDO pipeline YAML + packaging/verification scripts) and the npm publish path, which only runs during the official ship pipeline and is gated behind ESRP. The backport also pulls in the extension Corepack build migration (#17630) it depends on. Risk to already-shipping bits is low.
Regression?
No — this is net-new functionality, not a fix to something that regressed in 13.4.
Merge conflicts resolved
The auto
/backportfailed on conflicts, so this is manual. Conflicts were only in the extension build files (extension/Extension.proj,build.ps1,build.sh) — I took the PR's Corepack flow, since the PR also brings the Corepack bootstrap infra (install-corepack.yml,prepareCorepackYarn.mjs,corepack-version.txt) that 13.4 didn't have yet, and leaving those files on plainyarnwould've been inconsistent. release/13.4's own divergence was kept where it didn't conflict (extensionversionstays1.0.9; theaspireCliChannelOverrideplumbing from #17527 stays, with the PR's NodeTool + npm-verify steps on top). Verified the 15 core npm files are byte-identical to the source PR head, so nothing was dropped.