-
Notifications
You must be signed in to change notification settings - Fork 161
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)layersItems related to the Lambda Layers pipelineItems related to the Lambda Layers pipeline
Description
Summary
In 2.145.0 CDK made some changes to how custom resources and Node.js managed runtimes in AWS Lambda are managed (aws/aws-cdk#30108).
This broke our release pipeline, so we should downgrade until we know it's safe to upgrade again.
Why is this needed?
So that we can continue the release.
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.
Metadata
Metadata
Assignees
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)layersItems related to the Lambda Layers pipelineItems related to the Lambda Layers pipeline
Type
Projects
Status
Shipped