chore(deps): Keep aws-cdk dependencies in integration-test up to date #420
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 change?
We perform a check at CI time to ensure the version of aws-cdk libraries we're using are within 5 versions of the latest available.
If we're out of date, CI fails with instructions to run
./script/update-aws-cdk
. This script uses ncu (npm-check-updates) to update the aws-cdk dependencies.This change updates the call to ncu to:
Before (only checking
cdk/package.json
)After (checking
cdk/package.json
,eslint/package.json
andintegration-test/package.json
)See:
Does this change require changes to existing projects or CDK CLI?
No.
How to test
Run the
./script/update-aws-cdk
script?How can we measure success?
We update all aws-cdk dependencies in one go.
Have we considered potential risks?
n/a