generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 180
Open
Labels
internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Description
Summary
As stated in the Developer Guide for AWS Lambda, the Node.js 24 managed runtime is slated to be released in November 2025.
While this date is indicative only and subject to change, we should start working towards adding support for the runtime in Powertools for AWS Lambda (TypeScript).
Why is this needed?
So that we can migrate the project to use Node.js 24 as development environment and include the version in our test matrixes.
Which area does this relate to?
Other
Solution
Prerequisites
- AWS CDK should support the new managed runtime.
High level steps
- Update devcontainer & gitpod container
- Update GitHub Actions to use Node.js 24.x
- Update GitHub Issue templates
- Update contributing docs, nvm
- Add node version to test matrix both for unit & e2e tests
- Run all tests to ensure compatibility
- Merge & release
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Type
Projects
Status
Working on it