-
-
Notifications
You must be signed in to change notification settings - Fork 378
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
[PRO] EOL: update warming runtime to nodejs14.x #828
Comments
Refs #784 I just realized that a project I recently upgraded to Node.js 14 still uses Node.js 8 for warming. What do I need to do to update the warming lambda? I was expecting |
Hello! To update the warming functions you may need to delete and run |
Thanks!
Same comment as #784 (comment) 😄 . I'm not the one getting the e-mails, but my clients. But I'll communicate that this does not affect the services. |
Has this been fixed? I am running the latest 1.7.1-pro version, but when I ran
|
Hi @tj, just wonder if this warming function will be upgraded to nodejs14.x soon. I think that's a very useful feature of the pro version. However it is not working anymore for new applications since AWS has deprecated old node version. An update would be really appreciated. |
Bump to this request- this is one of the most important features that causes me to use the Pro version, please let us know when you'll be able to upgrade the warming function runtime? |
The "[Action Required] AWS Lambda end of support for Node.js 12" e-mails are rolling out, so we already missed one cycle. |
Prerequisites
up upgrade
)Description
AWS started sending out mails about nodejs10.x reaching EOL. The warming runtime cannot be changed by
up
users. Please upgrade to nodejs14.x (no need to go for 12 I guess).The text was updated successfully, but these errors were encountered: