Skip to content

Support Node 26 and drop 22-23 - #500

Open
alexluckett wants to merge 1 commit into
fix/v5-validation-messagesfrom
feature/node-v26-support
Open

alexluckett wants to merge 1 commit into
fix/v5-validation-messagesfrom
feature/node-v26-support

Conversation

@alexluckett

Copy link
Copy Markdown
Contributor

The plugin now supports Node 26 as well as Node 24.

Key changes

  • package.json and the root entry in package-lock.json: the engines range is now ^24.19.0 || ^26.0.0. The range lists each major version on its own, so that Node 25 and later versions that are not tested stay outside it.
  • check-pull-request.yml: the build, lint and test matrices run on Node 24 and 26. Node 22 and 23 are removed because the engines range does not include them. Node 23 is also end-of-life.
  • @types/node stays on ^24.19.2 on purpose. The types follow the lowest supported version, so that the type check rejects APIs that exist only in Node 26 and would fail at runtime on Node 24.

Widen the engines range to ^24.19.0 || ^26.0.0 and run CI on Node 24 and 26.
Node 22 and 23 leave the matrix because the engines range does not include them.
@types/node stays on 24 so that the type check rejects APIs that only exist in
Node 26.
@alexluckett
alexluckett force-pushed the feature/node-v26-support branch from 64155c8 to 2659d3b Compare November 19, 2026 14:38
@alexluckett
alexluckett marked this pull request as ready for review November 19, 2026 14:39
@sonarqubecloud

Copy link
Copy Markdown

@alexluckett
alexluckett added this pull request to stack #502 November 19, 2026 15:03

This branch has not been deployed

No deployments
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