Skip to content

chore!: minimum node version v22#4679

Draft
escapedcat wants to merge 2 commits intomasterfrom
chore/node-v22
Draft

chore!: minimum node version v22#4679
escapedcat wants to merge 2 commits intomasterfrom
chore/node-v22

Conversation

@escapedcat
Copy link
Copy Markdown
Member

BREAKING CHANGE: drop node v18 and v20 support

  • Bump engines to >=v22 in all 39 package.json files
  • Update @types/node to ^22.0.0
  • Update CI matrix to [22, 24]
  • Update Ubuntu baseline job to ubuntu:26.04
  • Update Dockerfile.ci, .mise.toml, .codesandbox/ci.json
  • Update pre-commit hook to use --ignore-engines
  • Update README and docs

escapedcat and others added 2 commits April 2, 2026 18:11
BREAKING CHANGE: drop node v18 and v20 support

- Bump engines to >=v22 in all 39 package.json files
- Update @types/node to ^22.0.0
- Update CI matrix to [22, 24]
- Update Ubuntu baseline job to ubuntu:26.04
- Update Dockerfile.ci, .mise.toml, .codesandbox/ci.json
- Update pre-commit hook to use --ignore-engines
- Update README and docs

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@knocte
Copy link
Copy Markdown
Contributor

knocte commented Apr 3, 2026

I'd recommend to jump major version after this, from v20.x to v22.x (this way it matches with node version required too).

@escapedcat
Copy link
Copy Markdown
Member Author

I'd recommend to jump major version after this, from v20.x to v22.x (this way it matches with node version required too).

This would skip directly from the current supported version 18 to 22 and drop both 18 and 22.
Commitlint versions will never really match the node versions by number I believe, sometimes it's just coincidence. If that's what you meant, not sure.

@knocte
Copy link
Copy Markdown
Contributor

knocte commented Apr 4, 2026

from the current supported version 18 to 22 and drop both 18 and 22.

I guess that was a typo? (drop both 18 and 20, not 18 and 22)

sometimes it's just coincidence

I'm not requesting this to be the case all the time, but yeah it would be nice to make it a coincidence now that we have to bump (instead of bumping from 20.x to 21.x).

@escapedcat
Copy link
Copy Markdown
Member Author

from the current supported version 18 to 22 and drop both 18 and 22.

I guess that was a typo? (drop both 18 and 20, not 18 and 22)

Ah, yes! :D

sometimes it's just coincidence

I'm not requesting this to be the case all the time, but yeah it would be nice to make it a coincidence now that we have to bump (instead of bumping from 20.x to 21.x).

Ah well, it's a hassle to take care of this. breaking changes can happen "all the time" anyways.

@knocte
Copy link
Copy Markdown
Contributor

knocte commented Apr 4, 2026

Talking about breaking changes, I guess you're planning on merging the other 2 PRs that have breaking changes too? (4629 and 4102)

@escapedcat
Copy link
Copy Markdown
Member Author

4629 yes
4102 I don't consider as ready currently, so no for now

@knocte
Copy link
Copy Markdown
Contributor

knocte commented Apr 4, 2026

What's left on 4102? I might give it a go.

@escapedcat
Copy link
Copy Markdown
Member Author

What's left on 4102? I might give it a go.

See the copilot comments and maybe that should be an option as well so people can turn it off if they do not like it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants