Skip to content

Every active repo builds and runs on a supported Node.js release #185

Open

Description

@ooloth

Current state

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

Activity

  1. 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
  2. ooloth commented on Nov 6, 2026

    @ooloth
    OwnerAuthor

    Two constraints from #217 for whichever Node release this picks:

  3. ooloth commented on Nov 7, 2026

    @ooloth
    OwnerAuthor

    #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.

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions