chore(ci): bump CI Node to 24 LTS + sync lockfile for npm 11 - #98
Open
seanspeaks wants to merge 1 commit into
Open
chore(ci): bump CI Node to 24 LTS + sync lockfile for npm 11#98seanspeaks wants to merge 1 commit into
seanspeaks wants to merge 1 commit into
Conversation
seanspeaks
force-pushed
the
chore/node-20-and-lockfile-sync
branch
from
August 20, 2026 01:02
a78b330 to
adb185a
Compare
seanspeaks
changed the title
seanspeaks
force-pushed
the
chore/node-20-and-lockfile-sync
branch
from
August 20, 2026 01:13
adb185a to
f13088e
Compare
seanspeaks
changed the title
Move CI onto the current Active LTS line (Node 24). Node 20 reached EOL on 2026-04-30 and `.node-version` was pinned to the long-stale 16.15.0. Node 24 ships npm 11, whose `npm ci` is stricter than npm 10 and rejected `next`'s lockfile (EUSAGE: "Missing encoding@0.1.13 / iconv-lite@0.6.3 from lock file"). Regenerated `package-lock.json` with npm 11 (`npm install --package-lock-only`) so `npm ci` is clean on Node 24 (verified: `npm@11 ci --dry-run` exits 0). The regen adds the missing encoding/iconv-lite entries and prunes some redundant optional/peer transitive dev-dep nodes; all six v1-ready workspace packages remain intact. - `.node-version`: 16.15.0 → 24 - `.github/workflows/release.yml`: setup-node 18 → 24 - `package-lock.json`: regenerated under npm 11 `engines.node` (`>=18`) already permits 24, so it's unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JDh45c1vm91ySYtvVv9Z65
seanspeaks
force-pushed
the
chore/node-20-and-lockfile-sync
branch
from
August 20, 2026 02:53
f13088e to
a185929
Compare
seanspeaks
changed the title
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.
What & why
Move CI onto the current Active LTS line (Node 24).
.node-version:16.15.0(long-stale) →24.github/workflows/release.yml:setup-nodenode-version: 18→24package-lock.json: regenerated under npm 11The lockfile part is required, not optional. Node 24 ships npm 11, whose
npm ciis stricter than npm 10 and rejectednext's current lockfile withEUSAGE: Missing encoding@0.1.13 / iconv-lite@0.6.3 from lock file(confirmed by a failing Node-24 run). Regenerating the lockfile with npm 11 (npm install --package-lock-only) adds the missing entries and prunes some redundant optional/peer transitive dev-dep nodes. Verified locally:npm@11 ci --dry-runexits 0, and all sixpackages/v1-ready/*workspace packages remain intact.engines.node(>=18) already permits 24, so it's left unchanged.🤖 Generated with Claude Code
Generated by Claude Code