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
Every active repo builds and runs on a supported Node.js release #185
Three active repos build or run on Node.js releases that no longer receive security fixes, and nothing tells anyone when a pinned release reaches end of life. This repo's .nvmrc pins v25.1.0, which reached end of life on 2026-06-01, and CI takes its Node version from that file. Two private repos pin v20.5.0 and v16.17.0, both past end of life. Dependabot doesn't read .nvmrc, so no update PR ever proposes a newer release.
Ideal state
CI and local development in every active repo use a Node.js release that is within its support period
A pinned Node.js release that is about to reach end of life is noticed before that date
Decisions
Constraints
No recorded decisions found (no docs/ directory; searched Markdown files for ADRs).
Open
No open decisions.
Starting points
.nvmrc: the pinned Node version
.github/workflows/ci.yml: reads node-version-file: '.nvmrc' in each job
changed the title [-]The site builds and deploys on a supported Node.js release[/-][+]Every active repo builds and runs on a supported Node.js release[/+]on Nov 5, 2026
#219 raised @notionhq/client to 5.30.0, which requires Node >=22. The Lighthouse floor of >=22.19.0 above already covers it. That PR regenerated the lockfile with npm 11.6.2, so the npm ci check after a Node bump applies to it.
Activity
[-]The site builds and deploys on a supported Node.js release[/-][+]Every active repo builds and runs on a supported Node.js release[/+]ooloth commentedon Nov 6, 2026
Two constraints from #217 for whichever Node release this picks:
lighthouse13.6.0 and@lhci/cli0.16.0 now require Node>=22.19.0, so the Lighthouse job needs at least that..nvmrcalso changes the npm CI gets with Node. build(deps): bump the npm-security group across 1 directory with 6 updates #217 showed a lockfile one npm accepts can failnpm ciunder another, so after the bumpnpm cihas to pass under the new bundled npm, unless Dependabot npm PRs install with the npm version CI runs #218 has pinned npm by then.ooloth commentedon Nov 7, 2026
#219 raised
@notionhq/clientto 5.30.0, which requires Node>=22. The Lighthouse floor of>=22.19.0above already covers it. That PR regenerated the lockfile with npm 11.6.2, so thenpm cicheck after a Node bump applies to it.