docs: the registry-side trusted publisher is owner work, not a given - #15
Merged
Conversation
The first two automated publish runs proved the workflow side end to end (PR driven to a tested merge, tags and releases cut, OIDC id-token minted) and then failed at the registry: ENEEDAUTH, npm finding no trusted publisher to exchange its token with. Record that state honestly instead of assuming the form is filled.
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.
The first two automated publish runs proved the workflow side end to end — release PR driven to a tested merge, tags and GitHub releases cut, OIDC id-token minted (run 1 even signed a provenance statement) — and then failed at the registry with
ENEEDAUTH: npm found no trusted publisher to exchange its token with. So the Trusted Publisher form on npmjs.com is not (correctly) in place yet forheaderless/vite-plugin-headerless. Record that honestly: it is owner work the automation can neither do nor verify, and until it matches, every automated publish fails this way.