Repository navigation
Explain the registry answer when npm publication fails - #540
Merged
Merged
Conversation
npm answers 404 both for a missing package and for an OIDC identity the Trusted Publisher does not name, so a failed publish hid the repository transfer's stale registration. Report the full registry answer and name the registration fields to check. Refs #536.
|
Caution Review failedThe pull request is closed.
|
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.
DISCLOSURE: LLM-GENERATED TEXT
Why: The
v0.2.0publish attempt ended with barenpm error code E404. npm uses 404 both for a missing package and for an OIDC identity its Trusted Publisher does not name, so the stale registration after the repository transfer looked like a generic registry failure.What:
npm publishfailsv0.2.0publication incident and the required registration updateRefs #536