docs: document forceAuth option for libnpmpublish #8789
+17
−0
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.
Description
This PR documents the \ orceAuth\ option for libnpmpublish, which is required when using automation tokens or when the \ oken\ option alone doesn't work.
Changes
Fixes
Closes #7091
Context
Users were experiencing 404 and 429 errors when trying to publish packages using automation tokens with libnpmpublish. The solution is to use \ orceAuth: { token }\ instead of just \ oken, but this wasn't documented. This caused significant confusion as mentioned in issue #4250 and #7091.
The \ orceAuth\ option is required in cases where the registry URL is not automatically detected from the token, which commonly happens with automation tokens.
Type of Change