Add optional NPM package release #15494
Merged
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.
This PR continues to improve our build and release pipelines:
.ado/scripts/npmPack.jsscript and fixed the PR validation by using this script for the CLI verification in.ado/templates/verdaccio-start.yml.PushNpmto.ado/release.ymlwith the improved steps:dist-tagcreated by thepublish.ymlpipeline as beforenpmPack,jsto check if the NPM packages were already published tonpmjs.com, removes all published packages from the local folder, and if any NPM packages left, then releases them tonpmjs.com.EsrpReleasetask is skipped if there are no packages to publish. It avoids to have an error that we observed before.As a test for the new
release.ymlpipeline I had released the 0.80.6 packages running it form a test branch.Microsoft Reviewers: Open in CodeFlow