You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dreamorosi opened this issue
Dec 15, 2022
· 1 comment
· Fixed by #1192
Assignees
Labels
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
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.
Should this be considered in other Lambda Powertools languages? i.e. Python, Java
The text was updated successfully, but these errors were encountered:
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
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.
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
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
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
The text was updated successfully, but these errors were encountered: