Skip to content

Maintenance: Support for Node.js 22 AWS Lambda managed runtime #3246

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

Closed
1 of 9 tasks
dreamorosi opened this issue Oct 23, 2024 · 2 comments · Fixed by #3327
Closed
1 of 9 tasks

Maintenance: Support for Node.js 22 AWS Lambda managed runtime #3246

dreamorosi opened this issue Oct 23, 2024 · 2 comments · Fixed by #3327
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

As stated I the Developer Guide for AWS Lambda, the Node.js 22 managed runtime is slated to be released in November 2024.

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 22 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 20.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

Future readers

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

@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Oct 23, 2024
@dreamorosi dreamorosi self-assigned this Oct 23, 2024
@dreamorosi dreamorosi moved this from Triage to Backlog in Powertools for AWS Lambda (TypeScript) Oct 23, 2024
@dreamorosi dreamorosi pinned this issue Oct 23, 2024
@dreamorosi dreamorosi linked a pull request Nov 18, 2024 that will close this issue
5 tasks
@github-project-automation github-project-automation bot moved this from Backlog to Coming soon in Powertools for AWS Lambda (TypeScript) Nov 20, 2024
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments 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 20, 2024
Copy link
Contributor

This is now released under v2.11.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 20, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Nov 20, 2024
@dreamorosi dreamorosi unpinned this issue Nov 22, 2024
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