| 2 Jun 2023 |
 raitobezarius | We opened an issue on affected packages for Node.js 16 | 13:37:54 |
| raitobezarius | IMHO, it's not worth it, we should only press on and ping the maintainers so the ping their respective upstreams on going to Node.js 18 at least | 13:38:08 |
| raitobezarius | No matter what, we will find ourselves in September pretty quickly and given my experience with saying hi to upstream, they need time to accomodate | 13:38:27 |
| raitobezarius | Adding a simple permittedInsecurePackages in the meantime is not too shocking and we allowed caching exceptions for Node.js 16 and OpenSSL 1.1 to make the ride less bumpy for everyone | 13:38:47 |
 Lily Foster | Yeah it's an upstream issue anyway. If your package needs 16, you can just enable insecure packages in nixpkgs 🤷♀️ | 13:39:02 |
 @adam:valkor.net | Yeah I figured we wouldn’t want to revert, just putting the question out there. | 13:39:46 |
| Lily Foster | In reply to @raitobezarius:matrix.org
We opened an issue on affected packages for Node.js 16 Oh really? Yeah how many are left? (Also were node maintainers pinged on that issue I don't remember seeing one other than the lists on the PR 🤔) | 13:40:04 |
| raitobezarius | airfield, base16-builder, netlify-cli, spacegun, n8n? | 13:40:35 |
| raitobezarius | are the remaining ones | 13:40:39 |
| raitobezarius | wait I'm not uptodate on master | 13:40:54 |
| Lily Foster | Okay that's not too bad. I thought netlify was already handled though | 13:40:58 |
| Lily Foster | And spacegun has been broken well before the 16 deprecation iirc | 13:41:13 |
| raitobezarius | apologies | 13:41:30 |
| Lily Foster | In reply to @lily:lily.flowers
Okay that's not too bad. I thought netlify was already handled though (Pretty sure I merged Robert's PR for that) | 13:41:36 |
| raitobezarius | we only have netlify-cli left on master | 13:41:36 |
| raitobezarius | then someone forgot to update the generate.sh | 13:41:50 |
| Lily Foster | Oh maybe I'm misremembering then | 13:41:50 |
