Skip to content
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

Use NODEJS_10_X for Lambda Runtime as NODEJS_8_10 is EoL on 31 Dec 2019 #132

Closed
trivikr opened this issue Oct 1, 2019 · 2 comments · Fixed by #133
Closed

Use NODEJS_10_X for Lambda Runtime as NODEJS_8_10 is EoL on 31 Dec 2019 #132

trivikr opened this issue Oct 1, 2019 · 2 comments · Fixed by #133
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged.

Comments

@trivikr
Copy link
Contributor

trivikr commented Oct 1, 2019

🐛 Bug Report

What is the problem?

Reproduction Steps

Verbose Log

N/A

Environment

N/A

@trivikr trivikr added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Oct 1, 2019
@rhboyd
Copy link
Contributor

rhboyd commented Oct 3, 2019

EOL from the Node.js Foundation doesn't mean EOL from Lambda support. historically, the Node versions have been supported by Lambda for some time after they are EOL by Node.js

@trivikr
Copy link
Contributor Author

trivikr commented Oct 3, 2019

EOL from the Node.js Foundation doesn't mean EOL from Lambda support.

I agree. Even though Lambda keeps supporting EOL versions, my suggestion is to recommend users to switch to new LTS in tutorials like this - especially when new LTS version is available.

@mergify mergify bot closed this as completed in #133 Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants