Skip to content

Use Node 26 for development and automation - #63

Merged
kvz merged 1 commit into
mainfrom
node26-tooling
Oct 21, 2026
Merged

kvz merged 1 commit into
mainfrom
node26-tooling

Conversation

@kvz

@kvz kvz commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

Move private development and automation to the patched Node 26 line so package builds, type checks, code generation, browser verification and release tooling exercise the runtime we use for maintenance.

  • Use ^26.12.1 in GitHub automation and 26.12.1 in .nvmrc; keep standalone Corepack 0.36.0 for Yarn.
  • Retain both Node 24 and 26 unit lanes and the public ^24.15.0 || >=26.0.0 runtime requirement.
  • Keep the hosted Vercel example on Node 24. Vercel supports only Node 22/24 and manages patch updates; changing the external automation process does not change that provider runtime.

Validated in a source archive without personal environment files using official Node 26.12.1 on Darwin arm64 (published SHA-256 verified):

  • Immutable Yarn 4.18.0 install with standalone Corepack 0.36.0.
  • yarn check: formatting/lint, TypeScript and 312 tests across 37 files pass. Existing nonfatal Biome diagnostics remain.
  • yarn pack including prepack compilation, and yarn example:build with a synthetic Convex URL pass.
  • yarn verify:local: all 13 local gallery browser tests pass. The existing cloud upload test belongs to the separate preview QA job.
  • Sharp PNG encode/decode, SWC TypeScript transformation and esbuild transformation pass; native Sharp/SWC bindings actually load on ABI 147.
  • Changesets CLI and the publishability guard load/run on 26; no publishing or production deployments performed.
  • Actionlint and council review pass.

Hosted validation: package build, Biome, TypeScript, component codegen, both Node 24/26 unit lanes, wedding example build and local browser suite all passed on this exact head. Vercel also built the preview successfully. The production job is correctly excluded from PR execution.

Hosted CI run 39666983160, attempt 2 is fully green at 2b067f3: all nine executed jobs pass. The cloud QA retry passed both the preview-backend check and full cloud verification; the original successful Node build/test results were retained.

The initial failure was missing branch-preview configuration. Provider inspection matched this exact Git head to the convex project, transloadit-com team and preview branch node26-tooling. Added only its public NEXT_PUBLIC_CONVEX_URL=https://astute-sandpiper-959.convex.cloud, without overwriting existing configuration, then rebuilt only that preview. No source, lockfile, environment files or production configuration changed.

Application behavior, dependencies and lockfile are unchanged.

🤖 Claimed by kvz on studio1/convex since 2026-10-21 · resume: codex resume 01a15e32-a05f-7153-89c2-0b1273795a49

@kvz kvz self-assigned this Oct 21, 2026
@vercel

vercel Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
convex Ready Ready Preview Oct 21, 2026 8:14pm UTC

Request Review

@kvz
kvz marked this pull request as draft October 21, 2026 20:07
@kvz
kvz marked this pull request as ready for review October 21, 2026 20:17
@kvz
kvz merged commit dd208a6 into main Oct 21, 2026
21 of 22 checks passed

This branch was successfully deployed

1 active deployment
Preview — 2b067f3b Deployed Oct 21, 2026 by vercel[bot]
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