Repository navigation
Move Node to 26 LTS everywhere at once - #211
Conversation
Node 26.13.0 (Lithium) is the first Node 26 LTS. Node 24 has been on security fixes only since 2026-10-20. Renovate's #209 moved only the two workflows. The @types/node hold in renovate.json5 says the types and the workflows must move in the same PR, so this PR moves all of them: - ci.yml and deploy-cloudflare.yml: node-version 24 -> 26 - src/vue: @types/node ^24.13.2 -> ^26.6.6 (lock: 24.19.2 -> 26.6.6) - renovate.json5: @types/node hold raised from <25 to <27 - .devcontainer/Dockerfile: Node v24.21.0 -> v26.13.0, with both checksums from nodejs.org's SHASUMS256.txt - CLAUDE.md: Node 24 -> Node 26 in Prerequisites and Devcontainer Supersedes #209. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Kd6o1asZ1umbDC4dVgANYJ
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Align Node runtime and tooling .devcontainer/Dockerfile, .github/workflows/ci.yml, .github/workflows/deploy-cloudflare.yml, src/vue/package.json, .github/renovate.json5, CLAUDE.md |
The development container and workflows now use Node 26. The @types/node version, Renovate settings, and documented prerequisites are updated to match. |
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Other
Possibly related issues
- Issue 41 in FactoryGameFan/FactorioTools tracks the same Node 24-to-26 update, including workflow pins and the
@types/nodeversion.
Merge Risk: 
Minimal · up to 24680
-
The Node 26 runtime, types, container pin, and Renovate configuration are aligned and mergeable.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Moves FactorioTools from Node 24 to Node 26.13.0, the first Node 26 LTS (Lithium, 2026-10-28). Node 24 has been on security fixes only since 2026-10-20.
Renovate's #209 changed only the two workflows. The
@types/nodehold in.github/renovate.json5says the types and the workflows must move in the same PR, or the types describe a runtime CI does not use. This PR moves every place that names Node 24, and supersedes #209..github/workflows/ci.yml,deploy-cloudflare.ymlnode-version: 24->26src/vue/package.json+ lock@types/node^24.13.2->^26.6.6(lock 24.19.2 -> 26.6.6, plus itsundici-types).github/renovate.json5@types/nodehold raised from<25.0.0to<27.0.0.devcontainer/Dockerfilehttps://nodejs.org/dist/v26.13.0/SHASUMS256.txtCLAUDE.mdChecked on tealc, Node 26.13.0 and npm 11.20.0
npm run build-wasm,npm run build(includes thevue-tsctype check against the new types) andnpm test: build OK, 55 tests passed.npx wrangler deploy --dry-run: read the 10 asset files, no errors.renovate-config-validatorfrom Renovate 44.205.2: config validated.v26.13.0and npm11.20.0. The arm64 checksum comes from the same SHASUMS file but was not built here.Merging deploys the site, since
deploy-cloudflare.ymlruns on every push tomain.🤖 Generated with Claude Code
https://claude.ai/code/session_01Kd6o1asZ1umbDC4dVgANYJ
Summary by CodeRabbit