-
Notifications
You must be signed in to change notification settings - Fork 14
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
Node 20 / 22 schedule #238
Comments
For reference, Node.js 22 was released today: |
Any Update concerning this ? |
We're wrapping up moving to fargate and other services. No one's been impressed with this communication over the years so feels risky going forward for us. Hopefully there'll be meaningful update for those hoping the service continues. Hopefully it starts to get maintained |
Node20 is the active version -- why is apprunner left at node18? https://nodejs.org/en/about/previous-releases |
Node 22 is now the active LTS version. So I hope I can upgrade soon my AWS lambda functions also to Node 22. |
Please provide a public estimated nodejs/any runtime release schedule and update the community with changes as they occur.
Nodejs20 is available on lambda and elsewhere.
Two years ago I requested that we have some basic insight into these plans for nodejs18 but this didn't occur and was quite frustrating. It appears (though I hope i'm mistaken) that the delay was due to some partial rewrite of node for some internal efficiency gains. While this may or may not be the case, this was not communicated and no meaningful visibility was provided. This one thing would give a minimal level of assurance to stakeholders.
Much appreciated in advance.
Community Note
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
Open a public schedule for stakeholders
Additional context
relates to 'Prepare and plan Node 18 deployment schedule #120' which never happened, it was released just before going into maintenance
The text was updated successfully, but these errors were encountered: