Repository navigation
docs(release): npm trust CLI flag and E409 recovery - #8373
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
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.
Two notes learned while testing the same release tooling end to end for react-native-ui-lib (wix/react-native-ui-lib#4056) on real npm:
npm trust github … --allow-publishis needed to allow direct publish from the CLI; npm 11.12.1 lacks the flag and fails with an unexplainedE400, 11.17.0 works.E409 Cannot publish over previously staged version; waiting until the version is visible and resuming again completes the release.Docs only.