‼️ NOTICE: aws-cdk CLI - "Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0"
See original GitHub issuePlease add your +1 👍 to let us know you have encountered this
Status: IN-PROGRESS
This is a bug in npm
version 7 only (npm
versions 6 and below work fine). See here for details: https://github.com/npm/cli/issues/3196
Overview:
After upgrading the CDK CLI package (aws-cdk
) with npm
version 7, running any CDK command in your CDK application fails with the error Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0
.
Complete Error Message
$ npx cdk ls
This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version.
(Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0)
Workaround:
Please remove the installed aws-cdk
package, and then install it again:
$ npm uninstall -g aws-cdk
$ npm install -g aws-cdk
Original opening post
This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version. (Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0)
aws-cdk version 1.103.0 and 1.104.0 do not work. aws-cdk version 1.102.0 works fine
Reproduction Steps
Install aws-cdk 1.103.0 (or 1.104.0) pip install -r requirements.txt
cdk ls
What did you expect to happen?
List of stacks displayed
What actually happened?
"This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version. (Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0) "
Environment
- CDK CLI Version : 1.104.0
- Framework Version: 1.103.0 & 1.104.0
- Node.js Version: v16.1.0
- **OS : Mac Big Sur
- Language (Version): Python 3.8.7
Other
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 2 years ago
- Reactions:84
- Comments:49 (27 by maintainers)
This is because schema version 16.0.0 was introduced in CDK 1.139. CDKv2 does not support it yet as of 2.5.0.
Solutions:
Best I can recommend at this moment is trying:
And seeing if that fixes it.
NPM left your install in an inconsistent state, and without being able to reproduce it it’s hard to say why.