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
Automate PR for removing EOL Node.js versions #2101
I think how infrequent and how little change it is, I would vote to not do this. It could prevent cases where the dates change last minute and aren't update here.
I am interested in the process on this. Is there a clear way to tell which base OS and Node.js version combinations should exist in the Docker registry? Since it is a manual process, I assume it depends on when y'all have landed those in the past?
The Package Maintenance WG maintains a tool called @pkgjs/nv which is basically a client library for schedule.json and https://nodejs.org/download/release/index.json. I was working on something this morning and think I need the docker builds and realized those files do not contain any information about the docker containers. Came here looking and saw this issue.
So I think there are two things that maybe can come out of this:
Use @pkgjs/nv in the process here to decide which versions to build
Augment @pkgjs/nv with additional data about which OS versions each Node.js version should have containers for
Activity
LaurentGoderre commentedon Jun 5, 2024
I think how infrequent and how little change it is, I would vote to not do this. It could prevent cases where the dates change last minute and aren't update here.
SimenB commentedon Jun 6, 2024
The release schedule exists as a JSON file - we should probably use data from that rather than duplicate its info into our own
versions.jsonfile.https://github.com/nodejs/Release/blob/main/schedule.json
Then we at least won't have stale data to compare to
wesleytodd commentedon Jul 1, 2025
I am interested in the process on this. Is there a clear way to tell which base OS and Node.js version combinations should exist in the Docker registry? Since it is a manual process, I assume it depends on when y'all have landed those in the past?
The Package Maintenance WG maintains a tool called
@pkgjs/nvwhich is basically a client library forschedule.jsonand https://nodejs.org/download/release/index.json. I was working on something this morning and think I need the docker builds and realized those files do not contain any information about the docker containers. Came here looking and saw this issue.So I think there are two things that maybe can come out of this:
@pkgjs/nvin the process here to decide which versions to build@pkgjs/nvwith additional data about which OS versions each Node.js version should have containers forThoughts on this?
nschonni commentedon Apr 27, 2026
Noting that in #2477, there are sometimes more changes that might need intervention, so I'm going to close this one