-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
AWS Custom resource generation upgrade from Node.js 16 to Node.js 18 #12310
Comments
tampueroc
changed the title
AWS Custom resource generation upgrade from Node.js 16
AWS Custom resource generation upgrade from Node.js 16 to Node.js 18
Dec 22, 2023
Duplicate of #12307 |
Hi, will this issue be addressed? Last time when Node.js 14 was deprecated by AWS many people complained that they couldn't run their CI/CD pipelines so a special release was made for v2. Is it possible to build a new special v2 release for Node.js 18 runtime some time before the deprecation occurs? Hence we can update our pipelines. Thanks |
any update or ETA? |
Yes, here is the related PR #12311 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Use case description
AWS sent a notification stateting that AWS Lambda ends support for Node.js 16 on July 24th 2024. Would it be possible to change defined runtime for Serverless v2
Proposed solution (optional)
Update addCustomResourceToService() runtime to
nodejs18.x
The text was updated successfully, but these errors were encountered: