Repository navigation
Node.js 20 End-of-Life action items #4306
Description
Capturing here things to do/tidy up when Node.js 20 goes End-of-Life.
- Update jenkins-workspace machines (used for linting) to Node.js 22 ansible: update jenkins-workspace machines #4305
- Update github-bot server to Node.js 22
- Update webhosts? (Webhooks are running on Node.js.)
- Identify remove/upgrade platforms that we no longer need to run
- FreeBSD ansible: remove freebsd #4365
- vs2019
Activity
[-]Node.js 20 End-of-Life[/-][+]Node.js 20 End-of-Life action items[/+]sxa commentedon May 12, 2026
FreeBSD was only built for Node 20. I have taken the two FreeBSD machines offline (they were also running java 17 so would have needed an update to continue to work after the upcoming jenkins update)
sxa commentedon Jun 11, 2026
@StefanStojanovic Do we still need the full set of six Windows machines in the release CI with Node.js 20 going out of support or are all active configurations still in use for one of the active versions?
StefanStojanovic commentedon Jun 12, 2026
Hey, I'm OOF until June 16. When I get back, I'll take a look at this. I was already planning to remove some of the Windows 2016 machines as they should be obsolete now, but I will check for other configurations. While we still need VS2019 machines in tests CI for addon tests, they may no longer be needed in the release CI (v24 is compiled on VS2022, but v22 might be compiled on VS2019).
ansible: remove freebsd (#4365)
StefanStojanovic commentedon Jun 17, 2026
@sxa I've checked this, and for Node.js v22+ only VS2022 is used for release builds, so we can remove the 3 VS2019 machines from the release CI.
StefanStojanovic commentedon Jun 18, 2026
I've finished removing the VS2019 machines from the release CI (Jenkins, Ansible, Rackspace, etc.) I will now look at the test CI as we have a bunch of VS2019 test configurations (and a few for compilation), to see what can be removed and cleaned up.