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.
What changes were made?
.npmrc
.npmrc
from the Actions workflowsNPM_TOKEN
to actionenv
to be read by the.npmrc
during the actionWhere were the changes made?
.npmrc
and GitHub actions workflowsHow have the changes been tested?
If the
.npmrc
is completely missing from the repo, it will be created by the changeset "Canary version" action. This commits that file back to the repo with our secret exposed. This is a problem! I have just tested another canary release with a blank.npmrc
which seems to prevent the exposed secret issue, however it does not seem to work for the actual publish.This change should make sure that
npmrc
is already in the repo so it should not need to be created during the changeset actionAdditional information
I followed this comment and their repo for this fix: changesets/action#98 (comment)
Don't forget to add a changeset if needed!