Skip to content

build(node): move to Node 26.12.1 (security release) - #1

Merged
evereq merged 1 commit into
developfrom
build/node-26.12.1
Oct 23, 2026
Merged

evereq merged 1 commit into
developfrom
build/node-26.12.1

Conversation

@evereq

@evereq evereq commented Oct 23, 2026

Copy link
Copy Markdown
Member

Node 26.12.1 security sweep (nodejs.org security release 2026-10-21): every pinned Node in the Ever fleet moves to 26.12.1.

file old new
.github/workflows/ci.yml actions/setup-node node-version: 22 node-version: 26.12.1

Notes

  • engines.node is >=20 (lower bound only) and @types/node is a caret range (^22.10.2), so both stay as they are.
  • This PR's own CI (typecheck, test, build, and the ESM + CJS resolve check) runs on Node 26.12.1, so a green run is the proof.
  • No release is cut: nothing publishes on push, and no version or tag changes here.

🤖 Generated with Claude Code

- .github/workflows/ci.yml: actions/setup-node node-version 22 -> 26.12.1

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@evereq

evereq commented Oct 23, 2026

Copy link
Copy Markdown
Member Author

AI-review check before merge: no AI bot left a review on this PR (only CodeQL ran, and it found nothing), so I reviewed the diff myself. It is one line in .github/workflows/ci.yml: node-version: 22 → 26.12.1. typecheck · test · build ran on Node v26.12.1 (setup-node log) and passed, including the ESM + CJS resolve check. No findings. Merging into develop (merge commit). No release or tag is cut.

@evereq
evereq merged commit f0fab39 into develop Oct 23, 2026
7 checks passed
@evereq
evereq deleted the build/node-26.12.1 branch October 23, 2026 18:22
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.

1 participant