fix(ci): drop upgrade step — Node 22 already supports OIDC provenance#12
Merged
fix(ci): drop upgrade step — Node 22 already supports OIDC provenance#12
Conversation
The install-g-latest step fails on the current runner (Node 22.22.2) with MODULE_NOT_FOUND: promise-retry. The upgrade was originally added to get OIDC provenance support, but Node 22 bundles a version that already supports it — the step is now both unnecessary and broken.
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.
Problem
The
Upgrade npm for OIDC supportstep (install -g latest) crashes on Node 22.22.2 runners:This was blocking every canary and release publish.
Fix
Drop the step entirely. Node 22 bundles a version that already supports OIDC provenance — the upgrade was only needed when older Node bundles were in use.
Applies to both
canaryandreleasejobs.