You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node 20 has been released. It is the "current" release and will be upgraded to LTS status later this year.
What should the user be able to do?
Run garden that has been built with the Node version 20.
Why do they want to do this? What problem does it solve?
This has the potential to directly solve some issues present on older runtime versions.
Suggested Implementation(s)
Read the release notes of both Node 19 and 20 for breaking changes, and then attempt the upgrade in a branch. Note to also update the necessary base images.
We should probably do this for the 0.13 branch / Bonsai release, as the 0.12 branch and release is already feature-frozen.
How important is this feature for you/your team?
🌹 It’s a nice to have, but nice things are nice 🙂
The text was updated successfully, but these errors were encountered:
Feature Request
Background / Motivation
Node 20 has been released. It is the "current" release and will be upgraded to LTS status later this year.
What should the user be able to do?
Run
gardenthat has been built with the Node version 20.Why do they want to do this? What problem does it solve?
This has the potential to directly solve some issues present on older runtime versions.
Suggested Implementation(s)
Read the release notes of both Node 19 and 20 for breaking changes, and then attempt the upgrade in a branch. Note to also update the necessary base images.
We should probably do this for the
0.13branch / Bonsai release, as the0.12branch and release is already feature-frozen.How important is this feature for you/your team?
🌹 It’s a nice to have, but nice things are nice 🙂
The text was updated successfully, but these errors were encountered: