Skip to content

ci: bump Node.js from 20 to 24 LTS#411

Open
kentkwu wants to merge 2 commits intoapache:mainfrom
kentkwu:gh-node-24-lts
Open

ci: bump Node.js from 20 to 24 LTS#411
kentkwu wants to merge 2 commits intoapache:mainfrom
kentkwu:gh-node-24-lts

Conversation

@kentkwu
Copy link
Contributor

@kentkwu kentkwu commented Mar 11, 2026

What's Changed

Node.js 20 LTS reaches end-of-life on April 30, 2026. Bumps from 20 to 24 LTS in CI

This does not change the required engine in package.json. It is only a CI change

Closes #410

@kou kou requested a review from Copilot March 12, 2026 06:53
@kou
Copy link
Member

kou commented Mar 12, 2026

This does not change the required engine in package.json. It is only a CI change

Does this mean that we keep supporting Node.js 20? If so, is it OK that we don't use Node.js 20 in our CI?

@trxcllnt @domoritz Do you have any concern that we require Node.js 24 or later?

Copy link

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.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@kentkwu
Copy link
Contributor Author

kentkwu commented Mar 12, 2026

@kou, the library requirements are still the same. So this change is not dropping support for 20. This is handled via package.json

  "engines": {
    "node": ">=20.0"
  },

However, the concern about dropping 20 in CI for tests is valid. I updated to matrix [20, 24] so we can test against current active LTS (24) and oldest maintenance LTS (20). Let me know if there are any objections.

@domoritz
Copy link
Member

No concerns about keeping up to date with new node versions.

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.

ci: bump Node.js from 20 to 24 LTS

4 participants