Skip to content

Maintenance: add support for nodejs18x runtime #1191

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 2 tasks
dreamorosi opened this issue Dec 15, 2022 · 1 comment · Fixed by #1192
Closed
1 of 2 tasks

Maintenance: add support for nodejs18x runtime #1191

dreamorosi opened this issue Dec 15, 2022 · 1 comment · Fixed by #1192
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

About a month ago, AWS Lambda added support for Node.js 18 in its managed runtimes.

We should add support to the runtime to the library, which involves updating the CI/CD workflows to make sure the Node.js version is used in unit & integration tests, as well as setting the version as main development version.

Why is this needed?

While we don't expect any significant change to be needed in the utilities, we need to add the new Node version to the unit and integration test matrixes so that we can have a higher degree of confidence on the fact that the library is compatible with the runtime.

Which area does this relate to?

Other

Solution

No response

Acknowledgment

@dreamorosi dreamorosi added triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Dec 15, 2022
@dreamorosi dreamorosi self-assigned this Dec 15, 2022
@dreamorosi dreamorosi linked a pull request Dec 19, 2022 that will close this issue
13 tasks
Repository owner moved this from Working on it to Coming soon in AWS Lambda Powertools for TypeScript Dec 19, 2022
@github-actions
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 the pending-release This item has been merged and will be released soon label Dec 19, 2022
@dreamorosi dreamorosi added completed This item is complete and has been merged/shipped and removed triage This item has not been triaged by a maintainer, please wait pending-release This item has been merged and will be released soon labels Jan 13, 2023
@dreamorosi dreamorosi moved this from Coming soon to Shipped in AWS Lambda Powertools for TypeScript Jan 13, 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
None yet
Development

Successfully merging a pull request may close this issue.

1 participant