chore: bump Node to v24.15.0 for npm OIDC trusted publishing#430
Merged
Conversation
The release-npm.yml workflow uses `node-version-file: .nvmrc` and publishes with `--provenance` via npm trusted publishing. npm OIDC trusted publishing requires npm CLI >= 11.5.1, which only ships with Node 24.x. Node 18 ships with npm 10.x, which causes the publish to fail with a 404 on PUT to the registry (as seen in v3.4.0 publish run 27569198051). Mirrors the fix applied in mixpanel-react-native-session-replay (commit 16a78159).
JianingL
approved these changes
Jun 15, 2026
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
2 participants
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
.nvmrcfrom18→24.15.0so the release workflow runs on a Node that ships an npm CLI new enough (≥ 11.5.1) for OIDC trusted publishing.Why
The v3.4.0 publish failed with:
This is the classic symptom of
npm publish --provenanceagainst npm trusted publishing when the npm CLI is too old to complete the OIDC exchange.release-npm.ymlreadsnode-version-file: .nvmrc, so18was loading npm 10.x.Mirrors the same fix applied in
mixpanel-react-native-session-replay(16a78159).CI (node.js.yml) hardcodes
[18.x]separately and is unaffected by this change.After merging
To retry the v3.4.0 publish, the existing
v3.4.0tag needs to be deleted and re-pushed from the newmastercommit so it satisfies therelease-npm.ymlancestor-of-master check.Test plan