Repository navigation
chore: upgrade to Node 26 LTS (26.13.0) - #37
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Upgrade CI, release builds, and
@types/nodeto Node 26 LTS. Node 26 entered Active LTS on 2026-10-28; 26.13.0 includes the October 2026 security fix from 26.12.1. Exact version pinned so the runner tool cache can't serve an older, unpatched 26.x.Files changed
.github/workflows/ci.yaml:testjobnode-version: 24→26.13.0;wasmjob22→26.13.0.github/workflows/release.yaml: bothnode-version: 22→26.13.0site/package.json+site/package-lock.json:@types/node^20.10.5→^26.6.6packages/workspaces/package.json+package-lock.json:@types/node^22.0.0→^26.6.6docs/local-harness.md(22+),site/docs/local.mdx(24+),site/docs/workspace.mdx(22+)Tested locally (Node 26.13.0, npm 11.20.0)
node --test site/scripts/install.test.mjs: oknpm --prefix packages/access test: oknpm --prefix examples/existing-app ci+run build: oknpm --prefix packages/workspaces ci+run build+test: oknpm --prefix site ci: oknpm --prefix packages/client ci+run build+test: oknpm --prefix packages/harness-host ci: oktarget/debug/tress,site/src/wasm/pkg,site/src/server/pkg-node):examples/existing-app test,site tsc --noEmit,harness-host build/test, and the cargo/site build steps. CI covers them.Left unchanged on purpose
enginesfloors:packages/workspaces>=20.19,packages/harness-host>=22,packages/accessandexamples/existing-app>=24. They already admit 26.cli.mjscheck,site/docs/reference.mdx,embedding.mdx,docs/setup.md,docs/fx-parity.md,packages/access/README.md,examples/existing-app/README.md).site/is built by Vercel; noenginesadded there (Vercel does not offer Node 26 yet).🤖 Generated with Claude Code