feat!: migrate action runtime and toolchain to node24 - #93
Merged
Merged
Conversation
This commit moves the GitHub Action runtime from `node20` to `node24`, in line with ReleaseMe, and aligns the build toolchain accordingly: - `action.yml` now runs `using: node24`; `engines.node` becomes `>=24` - `validate.yml` builds and tests on Node 24.x - `@tsconfig/node20` is dropped in favour of explicit compiler options targeting ES2024 - the same set ReleaseMe uses - `@types/node` is bumped to v24 The `typescript-eslint` v8 and `eslint-plugin-jest` v28 bumps are needed for the ES2024 target; the v6 parser rejects `es2024` in `lib`, and `eslint-plugin-jest` v27 pins the older `typescript-eslint` as a peer. That in turn drops the `func-call-spacing` and `type-annotation-spacing` rules from `.eslintrc.yml` as v8 no longer ships them - same as ReleaseMe, and Prettier already covers this. Note that `lib/` is unchanged; ncc emits identical bundles for the ES2024 target. BREAKING CHANGE: the action requires a runner with the `node24` runtime (Actions Runner v2.327.0 or newer). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Kevin-de-Jong
force-pushed
the
feat/node24-runtime
branch
from
September 16, 2026 12:35
1841b8d to
f96d51f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings CommitMe in line with ReleaseMe; the action now runs on the
node24runtime instead ofnode20.action.ymlswitches tousing: node24,engines.nodebecomes>=24andvalidate.ymlbuilds and tests on Node 24.x. The@tsconfig/node20base is replaced by the explicit compiler options ReleaseMe uses - ES2024 target andlib,module: nodenext.The dev-dependency churn follows from that;
@types/nodev24 needs a newer TypeScript, which needstypescript-eslintv8, which needseslint-plugin-jestv28. Two formatting rules (func-call-spacing,type-annotation-spacing) are dropped from.eslintrc.ymlas typescript-eslint v8 no longer ships them - same as ReleaseMe, and Prettier already covers this.Note that this is breaking for anyone on a self-hosted runner older than Actions Runner v2.327.0, which is where node24 action support landed.
Verified locally;
npm run lint,npm run test(37 passing) andnpm run buildare clean, and I smoke-tested the rebuiltlib/bundles for all three entrypoints (CLI help, pre-commit hook against a compliant and a non-compliant message, and the action failing as expected without a token).