Skip to content

feat!: remove Node 20 support - #231

Merged
pacostas merged 3 commits into
nodeshift:mainfrom
pacostas:update-node-versions
Jun 23, 2026
Merged

feat!: remove Node 20 support#231
pacostas merged 3 commits into
nodeshift:mainfrom
pacostas:update-node-versions

Conversation

@pacostas

Copy link
Copy Markdown
Member

Summary

Updates Node.js version support to align with current LTS releases.

Changes

  • Removed: Node.js 20 support
  • Added: Node.js 26 to CI matrix
  • Updated: Minimum engine requirement from >=20 to >=22
  • Updated: Release workflow to use Node.js 22 (from 16)
  • Updated: README prerequisites to reflect Node.js 22.x minimum

Current Active LTS Versions

  • Node.js 22 (Jod)
  • Node.js 24 (Krypton)
  • Node.js 26

All tests pass with the updated configuration.

@lholmquist

lholmquist commented Jun 23, 2026

Copy link
Copy Markdown
Member

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@pacostas
pacostas force-pushed the update-node-versions branch from b62f579 to c6e74c9 Compare June 23, 2026 18:44
@richardlau

Copy link
Copy Markdown
Member
  • Node.js 26

Note that Node.js 26 does not become LTS until October.

@pacostas

Copy link
Copy Markdown
Member Author

Note that Node.js 26 does not become LTS until October.

I agree, it practically tests the npm package against it, so is just an extra test in our case

@pacostas
pacostas merged commit ac82fba into nodeshift:main Jun 23, 2026
9 checks passed
@pacostas

Copy link
Copy Markdown
Member Author

Btw, i override it accidentaly, so Im adding it on this PR #233

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.

3 participants