fix(release): use Node 24 for npm OIDC trusted publishing#59
Merged
Conversation
npm 10.x (Node 22) cannot self-upgrade due to MODULE_NOT_FOUND error, and does not support OIDC publish auth natively. Node 24 ships with npm 11.x which supports the full trusted publishing flow. Node is only used here for npm publish — the project itself uses Bun.
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
Follow-up to #58.
npm install -g npm@latestfails on Node 22 withMODULE_NOT_FOUND(npm 10.x can't self-upgrade cleanly).npm install -g npm@lateststepnpm publish— the project uses Bun for everything elseTest plan
npm --versionshows 11.x+ in CI logs