fix(release): use npm publish for OIDC trusted-publisher auth#85
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pnpm publish does not pass the OIDC token needed for npm trusted publishers, causing 404 errors on every package. Switch to pnpm pack (to resolve workspace:* protocols) followed by npm publish (which supports OIDC auth via --provenance).
88ebc5a to
02b9c57
Compare
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.
Summary
pnpm publish --provenancetonpm publish --provenanceso OIDC trusted-publisher auth worksworkspace:*references are indevDependenciesonly, sonpm publishworks without resolutionThe v0.5.0 Release workflow failed because
pnpm publishdoes not pass the OIDC token needed for npm trusted publishers. This matches the working pattern in wterm.