Software Engineer at #IBM.
@nodejs Build Infrastructure, Releaser & Technical Steering Committee.
Release took a lot longer than planned today due to a last minute infrastructure issue caused by updating our indexing tool for the 27 alpha: https://github.com/nodejs/nodejs-dist-indexer/issues/110
It wasn't the 27 alpha changes that were at fault, and more that the existing tests didn't catch the breakage 😞.
First #nodejs 26 'Lithium' Long Term Support release, v26.13.0, is now out.
"Do all security vulnerabilities need to be fixed in private?"
https://openjsf.org/blog/sovereign-tech-agency-invests-in-openjs-to-rethink
OpenJS FoundationSovereign Tech Agency Invests in OpenJS to Rethink When Vulnerabilities Should Be Fixed in the Open | OpenJS FoundationResearch using Node.js will classify vulnerabilities by risk, then test whether some security issues can be fixed through normal open source development instead of behind closed doors