Skip to content

ci: use stable LTS Node versions instead of 'latest' - #373

Merged
connorjclark merged 1 commit into
mainfrom
ci-stable-node
Nov 5, 2026
Merged

connorjclark merged 1 commit into
mainfrom
ci-stable-node

Conversation

@connorjclark

Copy link
Copy Markdown
Collaborator

Summary

Replaces 'latest' in the CI Node matrix ([ 'latest', 'lts/*', 'lts/-1' ]) with [ 'lts/*', 'lts/-1', 'lts/-2' ] (currently Node 26, 24, and 22).

Why?

In actions/setup-node, node-version: 'latest' bypasses the actions/node-versions stable manifest and returns versions[0] directly from https://nodejs.org/dist/index.json without filtering out pre-release builds.

When v27.0.0-alpha.0.0.0 was published at the top of https://nodejs.org/dist/index.json, the basics (node latest) job began installing v27.0.0-alpha.0.0.0, causing yarn to fail the engines.node semver check:

error chrome-launcher@1.2.2: The engine "node" is incompatible with this module. Expected version ">=12.13.0". Got "27.0.0-alpha.0.0.0"

Using ['lts/*', 'lts/-1', 'lts/-2'] resolves against actions/node-versions with stable: true and tests the 3 active LTS lines (matching Lighthouse's CI matrix).

@connorjclark
connorjclark enabled auto-merge (squash) November 4, 2026 00:57
@connorjclark
connorjclark disabled auto-merge November 4, 2026 02:55
@connorjclark
connorjclark merged commit 9b543fe into main Nov 5, 2026
15 of 16 checks passed
@connorjclark
connorjclark deleted the ci-stable-node branch November 5, 2026 17:15
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.

2 participants