AWS CDK splits the CLI from the Construct Library (independent releases & new CLI repo)

Key update

AWS has split the Cloud Development Kit into two independently released components: the CDK Construct Library (the libs you depend on in apps) and the CDK CLI (the tool that synthesizes/deploys). The CLI source and release cadence are moving to a new GitHub repository and will follow its own version line (the first release on the new cadence will be 2.1000.0); the Construct Library remains on its existing 2.x line. AWS is explicitly not calling this “CDK v3” to avoid breakage, and they guarantee the newest CLI will continue to support previously released Construct Library versions.

Why it matters

This is a practical, developer-facing change — not a marketing tweak. Many CI scripts, automation playbooks, and install patterns assume a single CDK version (install both aws-cdk-lib and aws-cdk under the same version token). With separate release cadences, those assumptions break: you will need to install or upgrade the CLI and the Construct Library independently, and update any automation that pins a single CDK version for both pieces. Expect faster CLI iteration and more frequent tooling fixes (good), but also the potential for mismatches between CLI features and library behavior (something to validate in CI).

What to do now: stop assuming “one CDK version” in your scripts and CI images; install or upgrade the CLI and aws-cdk-lib separately and test synth/deploy steps when you change either; update any contributor or tooling docs that point to the legacy single-repo workflow and, if you contribute to the CLI, use the new CLI repository. For teams that pin CDK in reproducible builds, treat the CLI as a separate dependency to pin and test against — keep the CLI at a current 2.x release to ensure compatibility with new Construct Library releases.

Source

• Source