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
Sep 1, 2023
· 1 comment
· Fixed by #1666
Assignees
Labels
confirmedThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
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.
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
Sep 1, 2023
dreamorosi
added
confirmed
The scope is clear, ready for implementation
and removed
triage
This item has not been triaged by a maintainer, please wait
labels
Sep 1, 2023
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.
confirmedThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Summary
A few hours ago npm 10 was released and among other things it drops support for Node.js 14 and 16 which we still both support.
Why is this needed?
Since we are still running CI workflow for Node.js 14 and 16, we must pin the version 9.x of npm in order to continue running our CI pipelines.
Which area does this relate to?
Automation
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: