ci: upgrade npm in release.yml so Trusted Publishing works#50
Merged
Conversation
Node 20 ships with npm 10.x, but Trusted Publishing (OIDC) requires npm >= 11.5.1. Without this, `changeset publish` hits 404 on the registry because the OIDC token isn't accepted.
3 tasks
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
ubuntu-latestships with npm 10.xchangeset publishfails with 404s onnpm publisheven though the packages are configured as trusted publishers on npmjs.comThe last release workflow run after #47 merged failed exactly this way: all three packages at 0.7.2 have been versioned in-repo but never made it to the registry.
Test plan
main, finds no pending changesets, runspnpm release→changeset publishpayloadcms-vectorize@0.7.2,@payloadcms-vectorize/pg@0.7.2,@payloadcms-vectorize/cf@0.7.2land on npm