chore(deps): Update aws-cdk to 2.23.0

[jacobwinch]

Small follow up to #1251.

Whilst working on guardian/amiable#138, I copy & pasted the versions from peer dependencies without thinking about it. This mismatch leads to the following error when running cdk synth:

This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version.

This PR should help others to avoid this problem.

[akash1810]

Argh! Good catch! Looks like it was missed here, suggesting the script broke when we moved to V2?

[jacobwinch]

suggesting the script broke when we moved to V2?

Yes, I think you're right.

The command looks OK:

cdk/package.json

Line 27 in 6299a8a

"update-aws-cdk": "ncu \"aws-cdk-lib\" \"aws-cdk\" \"constructs\" --upgrade --deep --target minor",

My best guess is that it doesn't work correctly because aws-cdk is a peer dependency only:

cdk/package.json

Line 71 in 6299a8a

"aws-cdk": "2.23.0",

Because it's working OK with the integration tests, where it's a devDependency.

[akash1810]

It looks like ncu does not touch peerDependencies (see raineorshine/npm-check-updates#951). So it seems that asaws-cdk-lib is listed as a dependency and peer dependency in package.json, it's happily updated. Whereas aws-cdk is only listed as a peer dependency, so is left untouched.

A little confusing (as is most dependency management!). Not sure what to do... maybe add aws-cdk as a dev dependency to trick ncu?

[jacobwinch]

maybe add aws-cdk as a dev dependency to trick ncu?

Yeah it's a bit of a hack, but I think it's fairly harmless!

[github-actions]

🎉 This PR is included in version 43.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀