Discussed for Node.js 26, but shelved: #4197
Revisiting this for Node.js 27. Node.js 27 is expected to go End-of-Life at the end of April 2030.
RHEL 8 is scheduled to end maintenance support in May 2029.
In other words, if we build Node.js 27 releases on RHEL 8 our release machines would be on an unmaintained OS for almost an entire year at the end.
I'm proposing that we shift building the Linux binaries for Node.js 26 onwards to RHEL 9 (maintenance for that planned to end in May 2032). This would mean that the glibc requirements to run the official Linux binaries would raise from glibc 2.28 to 2.34 which will affect compatibility on popular Linux distributions:
| Distribution |
glibc |
Supported if binary built on RHEL 9 |
| Debian 10 |
2.28 |
❌ |
| Debian 11 |
2.31 |
❌ |
| Debian 12 |
2.36 |
✅ |
| Debian 13 |
2.41 |
✅ |
| RHEL 8 |
2.28 |
❌ |
| RHEL 9 |
2.34 |
✅ |
| RHEL 10 |
2.39 |
✅ |
| Ubuntu 20.04 |
2.31 |
❌ |
| Ubuntu 22.04 |
2.35 |
✅ |
| Ubuntu 24.04 |
2.39 |
✅ |
Discussed for Node.js 26, but shelved: #4197
Revisiting this for Node.js 27. Node.js 27 is expected to go End-of-Life at the end of April 2030.
RHEL 8 is scheduled to end maintenance support in May 2029.
In other words, if we build Node.js 27 releases on RHEL 8 our release machines would be on an unmaintained OS for almost an entire year at the end.
I'm proposing that we shift building the Linux binaries for Node.js 26 onwards to RHEL 9 (maintenance for that planned to end in May 2032). This would mean that the glibc requirements to run the official Linux binaries would raise from glibc 2.28 to 2.34 which will affect compatibility on popular Linux distributions: