Skip to content

Change Node.js version to 20 in CI workflow#741

Merged
bourgeoa merged 1 commit intomainfrom
bourgeoa-npm
Apr 13, 2026
Merged

Change Node.js version to 20 in CI workflow#741
bourgeoa merged 1 commit intomainfrom
bourgeoa-npm

Conversation

@bourgeoa
Copy link
Copy Markdown
Contributor

Updated Node.js version from 22 to 20 for compatibility.

Updated Node.js version from 22 to 20 for compatibility.
Copilot AI review requested due to automatic review settings April 13, 2026 12:45
@bourgeoa bourgeoa enabled auto-merge April 13, 2026 12:45
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Node.js version used in the CI workflow’s npm publishing job, aiming to improve compatibility for the publish step.

Changes:

  • Pin npm-publish-latest job to Node.js 20 during actions/setup-node.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 83 to 86
- uses: actions/setup-node@v6
with:
node-version: 22
node-version: 20 # required for OIDC npm@latest
registry-url: 'https://registry.npmjs.org'
Copy link

Copilot AI Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR title/description say CI is moving from Node 22 to 20 for compatibility, but only the npm-publish-latest job is pinned to Node 20. The build/test matrix still runs on 22 and 24 (and the artifact used for publishing is produced under Node 22), so Node 20 compatibility isn’t validated. Either add Node 20 to the build matrix / align the artifact build version with the publish job, or update the PR title/description to reflect that this change is only for the publish step.

Copilot uses AI. Check for mistakes.
@bourgeoa bourgeoa merged commit 0ea2510 into main Apr 13, 2026
11 checks passed
@bourgeoa bourgeoa deleted the bourgeoa-npm branch April 13, 2026 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants