chore: bump release workflow to Node 24 (ships npm 11)#21
Merged
StefanoGuerrini merged 1 commit intomainfrom Apr 21, 2026
Merged
chore: bump release workflow to Node 24 (ships npm 11)#21StefanoGuerrini merged 1 commit intomainfrom
StefanoGuerrini merged 1 commit intomainfrom
Conversation
Node 24 ships with npm 11.x, which supports OIDC and is newer than the Node 20 default (npm 10.x). The release job is independent of engines.node (which still declares >=20 for consumers); only the CI test job needs to match what users run.
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
Single-line change:
node-version: 20→24in.github/workflows/release.yml.Why
Node 24 LTS ships with npm 11.x, which supports OIDC publishing. Node 20 ships with npm 10.x (too old). This avoids the extra
npm install -g npm@lateststep we'd otherwise need in the publish job.engines.nodeinpackage.jsonremains>=20— that's the consumer requirement and is unaffected.ci.yml(test job) also stays on Node 20 so we keep testing against what users actually run.Test plan
ci.ymlruns here;release.ymltriggers only onrelease: published/workflow_dispatch)npm publish --provenanceworks without the global-npm-install step