-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maintenance: downgrade AWS CDK to 2.145.0 #2699
Comments
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. |
Reopening as the linked PR was merged too soon. Going to work on a new PR. |
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. |
This is now released under v2.3.0 version! |
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
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: