-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Node v20 image #954
Comments
Completely agree with your point. It would be highly beneficial for Balena to offer a continuous range of Node.js images, including the latest LTS version (currently 18.18.2) and keeping pace with the latest edge releases (like 20.8.1). This approach would help ensure that we are not missing out on important security patches and updates. For instance, the recent CVE-2023-44487, which led to a significant DDoS attack, underscores the urgency of staying up-to-date with Node.js versions. Having access to these updates in a timely manner is crucial for maintaining the security and stability of our applications. |
Any news on that from the balena team? It's 6 month now since the release of Node 20 as LTS... |
I think that there is a path to accomplish this now. I am able to get node20 working in bionic by following these build instructions: It should be fairly trivial to port the solution to a base image. |
@fritzdimmel @Petersdavis |
Is there plan to support node 20 for other builds? For example alpine? |
Hi, as Node16 just went to EOL, we updated our application to Node20. Right now the latest balenalib/%%BALENA_MACHINE_NAME%%-node:19-build image is v19.
Is there already a v20 in preparation so that we can move our devices to the v20? Any release date?
I see that v20 is going to be LTS by Oct 24 accourding to Releases but it would be good to be able to start now instead of going to v18 and in a month to v20.
Thanks
Fritz
The text was updated successfully, but these errors were encountered: