chore: pin Node.js to v24 (LTS)#687
Open
Shinyaigeek wants to merge 1 commit into
Open
Conversation
Standardize the toolchain on Node.js 24.18.0 (current LTS, "Krypton"): - Add a `.node-version` file so local tooling (nvm/fnm/mise/Volta) and CI resolve the same Node version. - Have both GitHub Actions workflows read the version from `.node-version` via `node-version-file` instead of a hardcoded `node-version: 20`, keeping a single source of truth. - Declare the requirement in package.json `engines.node` (exact match to `.node-version`). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
4 tasks
4 tasks
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.
Summary
Standardize the toolchain on Node.js 24.18.0 (current LTS, "Krypton").
.node-versionfile so local tooling (nvm / fnm / mise / Volta) and CI resolve the same Node version..node-versionvianode-version-file, instead of a hardcodednode-version: 20— single source of truth.package.jsonengines.node(exact match to.node-version).pnpm is intentionally left untouched here. Supply-chain hardening (pnpm bump + lifecycle-script allowlist + release-age cooldown + overrides migration) will follow in a separate PR, since pnpm 11 requires Node ≥ 22.13 and therefore depends on this bump landing first.
Test plan
Build JSworkflow installs Node 24.18.0 and builds greenPublish NPM packagesworkflow resolves Node 24.18.0🤖 Generated with Claude Code