You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ea9cef8
Browse filesBrowse the repository at this point in the historyBrowse files
`node-version: 24` was repeated in thirteen setup-node steps across seven
workflows with no single source. The number now lives in .nvmrc and
every step that follows a checkout reads it with `node-version-file`.
The one exception is the Vale publish job, which deliberately checks
nothing out while it holds an OIDC identity, so there is no file for
setup-node to read; it keeps a literal `node-version: 24` with a comment
pointing at .nvmrc.
24 is the choice because it is the Active LTS line today
(nodejs/Release schedule.json: LTS since 2025-10-28, maintenance from
2026-10-20). The Current line, 26, does not become LTS until 2026-10-28,
seven weeks out, and the local toolchain runs 24.14.0. packages/cli's
`engines.node` is a consumer-facing floor and is untouched.
0 commit comments