Bug: require specific `commons` version as dependency

[dreamorosi]

Expected Behavior

As a customer, when updating Logger, Metrics, or any of the other utilities I should be able to continue using them without having to worry about keeping consistency with the underlying commons package.

This is needed because we update our packages in lockstep, so if there's a change in the commons package new versions of the other packages (i.e. logger) will rely on the same version of the commons one.

Current Behavior

Currently the version range specified for the commons package uses the ^ symbol, which means updates to one of the utilities might not update the commons package depending on the update strategy.

Code snippet

N/A

Steps to Reproduce

This was originally reported here.

Possible Solution

No response

Powertools for AWS Lambda (TypeScript) version

latest

AWS Lambda function runtime

22.x

Packaging format used

npm

Execution logs

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments 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.