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 18 #3562

Open
1 of 2 tasks
dreamorosi opened this issue Feb 5, 2025 · 0 comments
Open
1 of 2 tasks

Maintenance: drop support for Node.js 18 #3562

dreamorosi opened this issue Feb 5, 2025 · 0 comments
Labels
internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) on-hold This item is on-hold and will be revisited in the future

Comments

@dreamorosi
Copy link
Contributor

Summary

Important

Starting from July 31, 2024 Powertools for AWS Lambda (TypeScript) will end support for Node.js 18.

This action is aligned with the date when AWS Lambda will mark the nodejs18.x runtime as deprecated and precedes the date after which you will no longer be able to create new functions using the runtime.

We recommend that you upgrade your existing Node.js 18 functions to Node.js 22 before July 31st, 2025.

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

You can use the following AWS CLI command to list all functions in a specific region using Node.js 18, 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=='nodejs18.x'].FunctionArn"

Why is this needed?

Starting from September 1st, 2025 we will no longer be able to deploy new Lambda functions using the nodejs18.x runtime, this means we will no longer be able to run integration tests for new code changes.

With this in mind, to ensure we can focus our efforts on supporting current runtimes, we will drop support for the runtime 4 weeks before that date.

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.) on-hold This item is on-hold and will be revisited in the future labels Feb 5, 2025
@dreamorosi dreamorosi moved this from Triage to On hold in Powertools for AWS Lambda (TypeScript) Feb 5, 2025
@dreamorosi dreamorosi pinned this issue Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) on-hold This item is on-hold and will be revisited in the future
Projects
Development

No branches or pull requests

1 participant