Closed
Description
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
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Python, Java