[G2M] npm - publish only to GitHub Packages - #69
Merged
Merged
Conversation
|
👋 Hello! I couldn't find a Notion Task URL in the PR description. Please add the full Notion Task URL to the PR body so I can keep everything in sync! ✨ (If you've already added it, please ensure it's a valid Notion URL.) |
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
1 participant
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.
Summary
Publishing
@eqworks/releasewent to GitHub Packages and then npmjs. The npmjs step is no longer used.v3.5.4also failed before it could publish, because the default Actions token is not allowed to write the organization package.Both tag workflows now publish only to GitHub Packages. The job grants
packages: writeso that token can publish, which is the same permissioncommon-loginuses. The changelog step authenticates to GitHub Packages when it installs the CLI.