use NODE_AUTH_TOKEN as environment variable name for the NPM_TOKEN secret - #266
Closed
yaacovCR wants to merge 2 commits into
Closed
use NODE_AUTH_TOKEN as environment variable name for the NPM_TOKEN secret#266yaacovCR wants to merge 2 commits into
NODE_AUTH_TOKEN as environment variable name for the NPM_TOKEN secret#266yaacovCR wants to merge 2 commits into
Conversation
🦋 Changeset detectedLatest commit: bfe9b96 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
yaacovCR
changed the title
NPM_TOKEN's environment variable name to official documentation
yaacovCR
changed the title
NODE_AUTH_TOKEN as environment variable name for the NPM_TOKEN secret
Member
|
We've decided to leave the npmrc handling to users or actions/checkout instead: #695 |
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
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.
depends on #267 which was extracted from this PR
context: #262 (comment)
in a follow-up PR, one could envision a
persist:falseoption that removes these files if the action actually created them so as to perform "clean up" similar to thepersist-credentials:falseoption foractions/checkout