Maintenance: bump version in `commons` prior to release

[dreamorosi]

Summary

Since version 1.11.1 the commons package exposes the current Powertools version as a module. This is used in other utilities and can be used also from customers to append the Powertools version as a persistent attribute to the Logger (example).

We don't have yet an automated process to bump the version in the file, so we need to do it manually.

Why is this needed?

So that the version in the module is in line with the actual version released on npmjs.com.

Which area does this relate to?

Other

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.

[github-actions]

This is now released under v1.12.1 version!