fix(release): use npm publish for OIDC trusted publishing#283
Merged
Conversation
Bump all @json-render/* packages to 0.19.0, add changelog entry for custom directives API and @json-render/directives package, and update the web app changelog page.
pnpm publish does not pass through OIDC credentials, causing E404 on npm. Switch to pnpm pack + npm publish per package, matching the pattern used in wterm.
Contributor
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.
Summary
pnpm -r publishtopnpm pack+npm publishper packagepnpm publishdoes not pass through OIDC credentials, butnpm publish --provenancehandles the token exchange natively