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

Maintenance: drop support for Node.js 14 #1664

Closed
1 of 2 tasks
dreamorosi opened this issue Aug 29, 2023 · 2 comments · Fixed by #1802
Closed
1 of 2 tasks

Maintenance: drop support for Node.js 14 #1664

dreamorosi opened this issue Aug 29, 2023 · 2 comments · Fixed by #1802
Assignees
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

Summary

Important

On November 23, 2023 Powertools for AWS Lambda (TypeScript) will end support for Node.js 14.

This action follows Node.js 14 reaching End-Of-Life (EOL) on April 30, 2023 and is scheduled just one business day before the date in which AWS Lambda will no longer apply security patches and other updates to the runtime.

We recommend that you upgrade your existing Node.js 14 functions to Node.js 18 before November 23, 2023.

End of support does not impact existing functions and functions using versions of Powertools for AWS Lambda (TypeScript) released before November 23, 2023, however starting from this date we will not guarantee compatibility with Node.js 14.

You can use the following AWS CLI command to list all functions in a specific region using Node.js 14, including published function versions:

Note

Make sure to replace the value of the --region flag and run this command in each region you have Lambda functions workloads

aws lambda list-functions --function-version ALL --region <Region> --output text --query "Functions[?Runtime=='nodejs14.x'].FunctionArn"

Why is this needed?

Starting from November 27, 2023 we will no longer be able to deploy new Lambda functions using the Node.js 14 runtime, this means we won't be able to run integration tests for new code changes.

With this in mind, we will stop supporting the runtime altogether.

Which area does this relate to?

Governance

Solution

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.

@dreamorosi dreamorosi added internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) confirmed The scope is clear, ready for implementation labels Aug 29, 2023
@dreamorosi dreamorosi self-assigned this Aug 29, 2023
@dreamorosi dreamorosi pinned this issue Aug 29, 2023
@dreamorosi dreamorosi moved this from Backlog to Working on it in Powertools for AWS Lambda (TypeScript) Nov 24, 2023
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Nov 24, 2023
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Nov 24, 2023
@dreamorosi dreamorosi unpinned this issue Nov 24, 2023
Copy link
Contributor

This is now released under v1.17.0 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Nov 24, 2023
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Development

Successfully merging a pull request may close this issue.

1 participant