Skip to content
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

Closed
1 of 2 tasks
dreamorosi opened this issue Jun 27, 2024 · 4 comments · Fixed by #2700 or #2702
Closed
1 of 2 tasks

Maintenance: downgrade AWS CDK to 2.145.0 #2699

dreamorosi opened this issue Jun 27, 2024 · 4 comments · Fixed by #2700 or #2702
Assignees
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) layers Items related to the Lambda Layers pipeline

Comments

@dreamorosi
Copy link
Contributor

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.

@dreamorosi dreamorosi added triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Jun 27, 2024
@dreamorosi dreamorosi self-assigned this Jun 27, 2024
@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation layers Items related to the Lambda Layers pipeline and removed triage This item has not been triaged by a maintainer, please wait labels Jun 27, 2024
Copy link
Contributor

⚠️ 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 github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Jun 27, 2024
@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation and removed pending-release This item has been merged and will be released soon labels Jun 27, 2024
@dreamorosi dreamorosi reopened this Jun 27, 2024
@dreamorosi
Copy link
Contributor Author

Reopening as the linked PR was merged too soon.

Going to work on a new PR.

Copy link
Contributor

⚠️ 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 github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Jun 27, 2024
Copy link
Contributor

This is now released under v2.3.0 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) layers Items related to the Lambda Layers pipeline
Projects
1 participant