GLSP-1594: Setup trusted publishing #1595
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
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.
What it does
Setup a combined publish workflow for npm trusted publishing.
This avoid having to rotate the publish token every 90 days (new NPM policy).
For each package you can setup one trusted workflow for CI publishing (using OIDC)
Part of #1594
How to test
Publishing has to be verified after merging (publish.yml has to exist on master). So we need to merge and then fix potential issues afterwards.
Not really more to test here. Other things like push triggers have to be tested/reevaluated after merging.
Follow-ups
Changelog