Conversation
Updated Node.js version in CI workflow from 22 to 20.
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions CI workflow to use Node.js 20 for the npm-publish-latest publishing job, while the rest of the workflow continues to use newer Node versions.
Changes:
- Switch
npm-publish-latestjob’sactions/setup-nodenode-versionfrom 22 to 20. - Retain npm upgrade step (
npm install -g npm@latest) for OIDC publishing flow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - uses: actions/setup-node@v6 | ||
| with: | ||
| node-version: 22 | ||
| node-version: 20 # for npm@latest | ||
| registry-url: 'https://registry.npmjs.org' |
There was a problem hiding this comment.
The PR title/description suggests the CI workflow’s Node.js version was changed from 22 to 20, but this change only affects the npm-publish-latest job. The main build job still tests Node 22/24 and npm-publish-dev still pins node_version: 22. Please either update the PR metadata to reflect the narrower scope or align the other jobs/versions as intended.
| node-version: 20 # for npm@latest | ||
| registry-url: 'https://registry.npmjs.org' | ||
| - name: Update npm to latest (required for OIDC) | ||
| run: npm install -g npm@latest |
There was a problem hiding this comment.
With npm-publish-latest running on Node 20, CI no longer validates the publish pipeline against the same Node version it publishes with (the build/test matrix is 22/24, and the release artifact is currently produced only when matrix.node-version == 22). Consider adding Node 20 to the test matrix and/or producing the publish artifact from the Node version you intend to support for publishing to avoid version-specific build/publish failures.
Updated Node.js version in CI workflow from 22 to 20.