Use NPM trusted publishing #2174
Open
+191
−182
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
Contributor
GCHQDeveloper581
left a comment
GCHQDeveloper581
left a comment
There was a problem hiding this comment.
Also be good to incorporate #2055 whilst significant changes are being made to workflows.
Member
Author
Yes good idea! Lets get that one merged first |
C85297
force-pushed
the
trusted-publishing
branch
from
7676a2a to
6bf75a5
Compare
Member
Author
|
@GCHQDeveloper581 Apologies for the formatting changes - I believe the way it is now formatted is the correct YAML format. However the diff is frustrating. Happy to re do it without changing the formatting if you'd prefer. I also updated the .editorconfig to correctly reflect the existing 2 space indent style. |
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.
Use NPM trusted publishing: https://docs.npmjs.com/trusted-publishers
Our existing token based flow for NPM publishing is no longer supported and our token was revoked.
The NPM registry should have now been setup to accept trusted publishing from this repo.