chore: removing npm token refs and adding trusted publishing config#3420
Closed
michaelmalave wants to merge 5 commits into
Closed
chore: removing npm token refs and adding trusted publishing config#3420michaelmalave wants to merge 5 commits into
michaelmalave wants to merge 5 commits into
Conversation
|
Git2Gus App is installed but the |
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.
Description:
This converts CLI publishing from using tokens which will be deprecated to trusted publishing.
Testing/Validation:
ensure this line is included in the publishing job file to ensure required permissions.
Limitation: Due to Github's configuration, workflows run are those on main. It is recommended to attempt a beta publish after merged to main.
Details:
NPM Trusted Publishing docs
Lerna: 9.0.0 is required for OIDC support for trusted publishing: lerna docs
Workspace discovery now happens automatically using the package.json in the
workspacesblock.NPM Trusted Publishing Configuration:

Related
W-20312941