Immutable solution version
Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0
Complete solution
This is caused by a bug in npm version 7 (npm/cli#3196) corrupting the aws-cdk CLI install, not by a real version mismatch. Reinstall the CLI using npm 6, or upgrade npm past the buggy 7.x range, then reinstall aws-cdk fresh.
The situation:
After upgrading the CDK CLI package with npm, every CDK command in the app failed with Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0, plus This CDK CLI is not compatible with the CDK library used by your application. The CLI and library versions looked compatible on paper. The root cause was a bug in npm version 7 itself, which broke the CLI install; npm 6 and below were unaffected.
What actually fixes it (verified in the thread):
This is caused by a bug in npm version 7 (npm/cli#3196) corrupting the aws-cdk CLI install, not by a real version mismatch. Reinstall the CLI using npm 6, or upgrade npm past the buggy 7.x range, then reinstall aws-cdk fresh. After a clean install with a working npm, the CLI and library schema versions line up again. The same class of error can also appear when the global CLI genuinely lags the library, so make sure the global aws-cdk is at the latest too.
Evidence
Someone asked: After upgrading the CDK CLI package with npm, every CDK command in the app failed with Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0, plus This CDK CLI is not compatible with the CDK library used by your application. The CLI and library versions looked compatible on paper. The root cause was a bug in npm version 7 itself, which broke the CLI install; npm 6 and below were unaffected. The verified answer: This is caused by a bug in npm version 7 (npm/cli#3196) corrupting the aws-cdk CLI install, not by a real version mismatch. Reinstall the CLI using npm 6, or upgrade npm past the buggy 7.x range, then reinstall aws-cdk fresh. After a clean install with a working npm, the CLI and library schema versions line up again. The same class of error can also appear when the global CLI genuinely lags the library, so make sure the global aws-cdk is at the latest too. Full thread: https://vectle.com/threads/thr_WO2Fec6KxfdDPvh4WiuciQ
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_VCTco0pFU4OmhGlcu3tHSw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloud assembly schema version mismatch: Maximum schema version supported is 10.0.0, but found 11.0.0 <span>— Vectle</span></a>