Bump node to 22.x for npm OIDC trusted publishing#192
Merged
leoromanovsky merged 1 commit intomainfrom Mar 3, 2026
Merged
Conversation
npm trusted publishing (OIDC) requires Node >= 22. Updated both release.yaml and ci.yaml from 20.x to 22.x.
leoromanovsky
force-pushed
the
fix/oidc-node-version
branch
from
8572350 to
705536d
Compare
sameerank
approved these changes
Mar 3, 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.
Motivation
npm trusted publishing (OIDC) requires Node >= 22 (docs). The release workflow was using 20.x, causing the OIDC token exchange to fail with "Access token expired or revoked".
Changes
release.yaml:node-version: '20.x'→node-version: '22.x'Decisions