chore: set up trusted publishing#634
Draft
lukasmatta wants to merge 1 commit into
Draft
Conversation
Coverage report for library
Test suite run success830 tests passing in 30 suites. Report generated by 🧪jest coverage report action from be75e95 |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the CPS UI Kit publish workflow to move toward npm “trusted publishing” by enabling GitHub OIDC and removing the use of a long-lived npm auth token.
Changes:
- Adds GitHub Actions
id-token: writepermission to support OIDC-based publishing. - Removes
NODE_AUTH_TOKENfrom thenpm publishstep.
Playwright test resultsDetails
|
27d192e to
be75e95
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sets up https://docs.npmjs.com/trusted-publishers
Closes #497