ci: migrate to npm trusted publishing #1967
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
CI uses NPM_TOKEN secret for publishing packages to npm. Classic tokens have been revoked by npm and granular tokens expire every 90 days.
Issue Number: N/A
What is the new behavior?
Uses npm Trusted Publishing with OpenID Connect (OIDC) - no tokens needed, more secure.
Does this PR introduce a breaking change?
Other information
Prerequisites before merging:
Set up Trusted Publisher on npm for each package at
https://www.npmjs.com/package/@angular-builders/<pkg>/access:ci.ymljust-jebangular-buildersAfter merging, the
NPM_TOKENsecret can be deleted from GitHub.