Maintenance: manually bump aws-cdk in layers and examples

[dreamorosi]

Summary

The version of aws-cdk lib present in the lock file (2.155.0) doesn't match the version of aws-cdk-lib also installed (2.161.0). This causes a mismatch at runtime which was not detected in the e2e tests but caused the release pipeline to fail (failure state is recoverable).

We'll investigate changes to the e2e pipeline to catch this type of issue, but for now we'll manually bump the version to progress with the release.

Why is this needed?

So that we can continue deploying the Lambda layers.

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

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.

[github-actions]

This is now released under v2.9.0 version!