[cli] Cloud assembly schema version mismatch
See original GitHub issue❓ General Issue
The Question
I installed aws-cdk.aws-athena. Now the stack is not able to be synthesized with the following error:
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 6.0.0, but found 7.0.0)
I tried npm install -g aws-cdk
to upgrade the CDK CLI but the error remains.
Environment
- CDK CLI Version: 1.72.0
- Node.js Version: v15.2.0
- OS: OSX
Other information
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:16 (1 by maintainers)
Top Results From Across the Web
‼️ NOTICE: aws-cdk CLI - "Cloud assembly schema version ...
NOTICE: aws-cdk CLI - "Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0" #14738.
Read more >How to solve CDK CLI version mismatch - Stack Overflow
I encountered this issue with a typescript package, after upgrading the cdk in package.json. As Maciej noted upgrading did not seem to work....
Read more >aws-cdk/cloud-assembly-schema module - AWS Documentation
The schema version is specified in the cloud-assembly.version.json file, under the version property. It follows semantic versioning, but with a small twist.
Read more >@aws-cdk/cloud-assembly-schema - npm
The schema version is specified in the cloud-assembly.version.json file, under the version property. It follows semantic versioning, ...
Read more >Hi, I'm working on the AWS CLI and I keep getting | Chegg.com
Please upgrade the CLI to the latest version. (cloud assembly schema version mismatch: Maximum schema version supported is 21.0.0, but found 22.0.0) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Faced the same issue. Fixed by :
pip install -r requirements.txt
Hi @nemanjko - Thanks for the challenge. I have some results, but I am not sure if we still can qualify them as “elegant”.
Refusing to start removing all, I wanted to explore what could be causing the issue. The error message says that you need to upgrade your CDK CLI, but we both did it and the error persisted.
What I have seen in my case is, even if I ran:
and got a successful installation of v1.74.0, the output of
cdk --version
was still v.1.72.0. What was happening was that the symbolic link was pointing to a wrong path (I don’t know why).They way I fixed the problem was:
I hope this brings some information to find the root cause (points to NPM though) and help other people.