Test Cypress compatibility with Node.js 26

[AtofStryker]

Overview

Node.js 26.x is the next even-numbered (LTS-track) major line. We should run Cypress’s tests against Node.js 26, extend binary coverage where appropriate, and update documentation—similar to the Node.js 24 compatibility request (#31581).

Background

• Node.js 26 follows Node.js 24 on the established April “Current” cadence for even majors, with promotion to Active LTS in October of the same calendar year (per the Node.js project’s published schedule).
• Early validation reduces surprises for teams upgrading CI images, local environments, and any workflows pinned to newer Node majors.
• Exact calendar dates are planned and can move; the Node.js project states schedule changes are communicated with notice (see the Release working group / schedule documentation).

Node.js project timeline (authoritative sources)

The Node.js project publishes lifecycle dates as machine-readable JSON in nodejs/Release → schedule.json (on main).

As of the current schedule.json entry for v26:

Milestone	Planned date
Initial release (start)	2026-04-22
Active LTS (lts)	2026-10-28
Maintenance LTS (maintenance)	2027-10-20
End of Life (end)	2029-04-30

Helpful related links from the Node.js organization:

• Release schedule + policy context: github.com/nodejs/release (includes the human-readable schedule table; it may briefly lag schedule.json right around a new major cut).
• Official “Previous releases” overview: nodejs.org — Previous releases
• Upcoming cadence change (annual majors from 2027): nodejs.org — Evolving the Node.js release schedule — this post describes Node.js 26 as the last major line under the current six-month major / even-LTS model before the transition described there.

Note: If the Node.js release team adjusts dates, treat schedule.json on main as the source of truth and update the table above accordingly.

Proposed work

1. Run Cypress’s test suite(s) against Node.js 26.
2. Add/extend binary system tests for Node.js 26 (pattern from prior Node major bumps), e.g. system-tests/test-binary/node_versions_spec.ts.
3. Additionally:
   • Validate binary installation on Node.js 26.
   • Validate binary execution and core workflows.
   • Confirm binary resolution in typical Node.js 26 environments (images, version managers, etc.).
4. Update documentation to reflect Node.js 26 support status in cypress-io/cypress-documentation once verified.

Success criteria

• Binary system tests pass for Node.js 26 in CI.
• Documentation reflects Node.js 26 support status.
• No regressions for existing supported Node versions.

Additional context

• Prior similar request: #31581 (Node.js 24).

[AtofStryker]

Looks like current plan is to release node 26 on May 4th. see cypress-io/cypress-docker-images#1488 (comment)

[MikeMcC399]

They're now writing May 5, 2026 in the PR that will release Node.js 26.0.0, however there hasn't been any update to:

• https://github.com/nodejs/release#readme or
• https://github.com/nodejs/Release/blob/main/schedule.json

so any forward-looking dates need to be viewed with caution.

The original planned date 2026-04-22 definitely did not happen though.