[0.80] Release NPM packages in publish pipeline #15483
Merged
Conversation
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
anupriya13
approved these changes
Dec 17, 2025
This was referenced Dec 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry pick PR #15482
The PR also added the new
.ado\scripts\npmPack.jsscript that creates all NPM packages and can reduce their count against the published packages innpmjs.com. We are going to use it as a building block to improve our build pipelines instead of usingbeachball publish. Thebeachballis going to be used only for version bumping.In this PR we were able to run all CLI validation tests because they run against NPM packages that we built inside of this PR instead of taking thier versions from npmjs.com.
Microsoft Reviewers: Open in CodeFlow