-
Notifications
You must be signed in to change notification settings - Fork 161
Closed
Labels
automationThis item relates to automationThis item relates to automationcompletedThis 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 #3958 we moved the dev environment to use ESM by default, we however forgot to update the usage of a specific CJS feature in the layers
part of the codebase which causes the release CI to fail.
Why is this needed?
We should fix it so that we can continue the release.
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.
Metadata
Metadata
Assignees
Labels
automationThis item relates to automationThis item relates to automationcompletedThis 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