3 ms·
You realize they have a schedule pattern right and they probably didn't realize openssl EOL was in the middle of a LTS lifecycle.
by joshmanders 4y ago
You realize they have a schedule pattern right and they probably didn't realize openssl EOL was in the middle of a LTS lifecycle.
- linkgoron 4y agoThe dates were known in advance - however, the Node.js team expected OpenSSL 3 to be out before the release of Node 16, but it didn't happen - so they had to release with OpenSSL 1.1.1. I think that there was some minor hope of maybe upgrading, but obviously it was too backwards-compatibility breaking to land without a new major. https://github.com/nodejs/TSC/issues/1222 https://github.com/nodejs/TSC/issues/1222 https://github.com/nodejs/TSC/pull/859 https://github.com/nodejs/TSC/pull/859