chore: Automate cdk upgrade #468
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Automate the cdk upgrade flow. To do this I created a script to parsed the cdk version out of the projen rc file, then check the npm version from 1 month ago. I chose that because that's the minimum version that someone needs, so 1 month behind seemed like a middle ground between being recent enough and not being so aggressive that someone is constantly having to upgrade cdk because of us. Let me know if you prefer a different value for this. If they don't match, update it. I tested this locally and it seems to work, I'll run it manually once this is merged to know for sure. The script has to be included in the github upgrade workflow, so we have to overwrite it in projen since its managed for us. Issues: #465 Projen docs about this: https://projen.io/docs/project-types/aws-cdk-construct-library/#depending-on-aws-cdk-lib
TalUsvyatsky
approved these changes
Aug 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Automate the cdk upgrade flow. To do this I created a script to parsed the cdk version out of the projen rc file, then check the npm version from 1 month ago. I chose that because that's the minimum version that someone needs, so 1 month behind seemed like a middle ground between being recent enough and not having someone have to go back and forth between upgrading the datadog cdk constructs and cdk versions, if they're doing some kind of weekly upgrade like we usually have. Let me know if you prefer a different value for this.
The script has to be included in the github upgrade workflow, so we have to overwrite it in projen since its managed for us.
Projen docs about this: https://projen.io/docs/project-types/aws-cdk-construct-library/#depending-on-aws-cdk-lib
Motivation
The CDK version is getting out of date, we're about 7 months behind: Issues: #465
Testing Guidelines
I tested this locally and it seems to work, I'll run it manually once this is merged to know for sure.
Types of Changes
Check all that apply