-
Notifications
You must be signed in to change notification settings - Fork 393
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.js 16 is now 'End of Life' #5422
Comments
Reopen in favor of #5432 |
Hi @iamhopaul123 , has this been implemented? |
Hello @CameronMcAuley
Thanks for your patience! |
@KollaAdithya what is the timeline for this upgrade? This has been flagged here at UCLA as a potential issue across accounts using copilot. Operationally, we are required to create upgrade and deprecation roadmaps aligned with EOL for various dependencies and their versions. Generally speaking, this allows us to migrate to new versions 3-6 months before their deprecation. Hoping to get something on our board for this so we can upgrade ASAP. |
@h5aaimtron sorry about the trouble! this is one of the top tasks on the list - we'll roll out the upgrade asap, and update the status here 🙇🏼♀️ ! |
Hello @CameronMcAuley and @h5aaimtron ! Nodejs 16.x is now upgraded to nodejs20.x and now released in v1.33 Upgrade to Copilot version v1.33 and run |
https://nodejs.org/en/blog/announcements/nodejs16-eol
'We are moving the End-of-Life date of Node.js 16 by seven months to coincide with the end of support of OpenSSL 1.1.1 on September 11th, 2023.'
With the newest version of the copilot-cli, generated Lambdas still use Node.js 16 which is EOL.
Are there any plans to upgrade this to 18 or 20?
The text was updated successfully, but these errors were encountered: