Repository navigation
ci: say npm refused the token, not why - #319
Merged
Merged
Conversation
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.
#317's error message and comments said npm granular tokens "expire after at most 90 days". npm's documentation doesn't say that. It only requires the expiry to be at least a day away and gives no maximum. What we observed is narrower: the token was set 93 days ago, and
npm whoamiwith it now returns401 Unauthorized. The token may have expired, or it may have been revoked.The error now says what was seen and keeps the cause as a possibility:
NPM_TOKEN was refused (…401…); it may have expired or been revoked.The script's comment, the release.yml comment and #317's CHANGELOG line are corrected to match. I also corrected #317's PR body and #318, which made the same claim.