Repository navigation
ci(release): gate npm publishing behind NPM_AUTOPUBLISH - #3
Merged
Merged
Conversation
A bad repository token made the npm job fail the whole v0.6.0 release run even though the GitHub release and host assets were published. Automatic publishing now requires both the NPM_AUTOPUBLISH repository variable and a valid NPM_TOKEN; manual `npm publish` remains the default.
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.
The v0.6.0 npm job failed on an invalid repository token while the release assets succeeded. Automatic npm publishing now requires
NPM_AUTOPUBLISH=trueplus a validNPM_TOKEN; manualnpm publishremains the default.