Maintenance: pin npm 9.x in our CI

[dreamorosi]

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

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• 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.

[github-actions]

⚠️ 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.