fix: update npm publish workflow to use new secret#28
Open
dtjones404 wants to merge 1 commit into
Open
Conversation
- Update actions/checkout@v2 to v3 - Update actions/setup-node@v2 to v3 - Change fetch-depth to ref for consistency - Update to KRAKENJS_PAYPAL_SDK_NPM_AUTH_TOKEN secret - Add workflow_dispatch documentation - Update publish step name
dtjones404
force-pushed
the
fix/update-npm-token-secret
branch
from
fe8e6aa to
9857cc3
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
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.
Updates the npm publish workflow to use the new
KRAKENJS_PAYPAL_SDK_NPM_AUTH_TOKENsecret instead of the deprecatedNPM_TOKEN.This change:
NPM_TOKENtoKRAKENJS_PAYPAL_SDK_NPM_AUTH_TOKENThis is analogous to the changes made in paypal/paypal-applepay-components#20