Skip to content

Move CI and Docker to Node 26 LTS, and align @types/node #244

Closed

Description

@shockalotti

From discussion #240 (c-nv-s), following the Node.js October 2026 security releases.

Finding

CI and Docker both run node:22, while frontend/package.json pins @types/node at ^26.6.5. Types and runtime already disagree, so the type definitions describe an API the build does not run on.

Node status as of Nov 2026

  • October 21 2026 security releases: fixed versions 22.23.4, 24.22.1, 26.12.1. Four of ten CVEs rated High.
  • Node 22: Maintenance LTS, EOL April 2027.
  • Node 24: Maintenance LTS since 20 Oct 2026, EOL April 2028.
  • Node 26: Active LTS since 28 Oct 2026, EOL April 2029.

Work

  1. Dockerfile frontend-builder stage: node:22-alpine -> node:26-alpine
  2. .github/workflows/ci.yml node-version: 22 -> 26
  3. .github/workflows/audit.yml node-version: 22 -> 26
  4. frontend/package.json @types/node already ^26.6.5, so it becomes honest; bump to the current 26.x if needed
  5. Confirm pnpm build and the single-binary make build still pass, and that corepack prepare pnpm@10.32.1 still works on the new base image

Notes

Node 26 is the last release line under the old schedule; from Node 27 the project moves to one major release a year with every release becoming LTS (October 2027).

Discussion: #240

Activity

  1. pullfrog commented on Nov 10, 2026

    @pullfrog
    Contributor
  2. added a commit that references this issue on Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions