fix/cdk-cli
safe381b3cb · fullPR #335reviewed 2026-07-22 23:27 UTC0H · 0M · 0L · 1IThe branch
- Purpose
- Unblock staging and prod CDK deploys after the aws-cdk-lib bump in PR #329 caused a cloud-assembly schema version mismatch (CLI max schema 49, lib emitting schema 54).
- Goal
- Raise the aws-cdk CLI floor to ^2.1132.0 so all CDK deploy/synth/diff commands work with aws-cdk-lib@2.260.0.
- Sub-goals
- SG-1: Bump aws-cdk devDependency floor in infra/cdk/package.json
- SG-2: Re-resolve pnpm lockfile for the updated aws-cdk package
The changes (whole branch)
- What
- One-line change in infra/cdk/package.json (aws-cdk ^2.213.0 → ^2.1132.0) plus the pnpm lockfile update resolving aws-cdk from 2.1034.0 to 2.1132.1.
- Why
- aws-cdk-lib@2.260.0 (bumped by Dependabot in PR #329) emits cloud-assembly schema 54, but the CLI was locked at 2.1034.0 which reads at most schema 49. Every cdk diff/deploy/synth was failing with 'Cloud assembly schema version mismatch'. Staging was stuck and the release-promote CDK→prod step would have hit the same failure.
- Areas
- infra/cdk/package.json+1−1pnpm-lock.yaml+41−10
- Blast
- 2 files, +42/−11. CDK tooling only — no runtime code, no app logic, no Lambda handlers, no stacks changed.
hotfix unblocks-staging unblocks-prod-promote
➖CI/typecheck· CI status not accessible via personal access token➖coderabbit· No .coderabbit.yaml in repo
Findings · 1
correctness1
info
Pre-existing: constructs@10.4.4 violates aws-cdk-lib@2.260.0 peerDep (requires ^10.5.0)
infra/cdk/package.json:15
aws-cdk-lib@2.260.0 declares peerDependencies: { constructs: '^10.5.0' } but the package.json pins constructs@^10.4.2 (resolved 10.4.4). pnpm's autoInstallPeers silently ignores the mismatch. The constructs API is stable across minor versions so no runtime failure, but the declared peer dep is violated. Introduced by the Dependabot aws-cdk-lib bump (#329), not by this PR — follow-up bump of constructs to ^10.5.0 is the fix.