Repository navigation
chore: bump aws-cdk-lib to ^2.254.0 (fixes Windows Node EINVAL) - #3317
Merged
Merged
Conversation
Raise the aws-cdk-lib peer dependency floor from ^2.234.1 to ^2.254.0 across all packages and refresh the lockfile (resolves to 2.267.0). This picks up the upstream fix for a crash during asset fingerprinting on Windows with newer Node.js releases, where fs.openSync was called with O_SYNC|O_DSYNC and failed with EINVAL. The fix shipped in aws-cdk-lib 2.254.0.
🦋 Changeset detectedLatest commit: 86211d1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 15 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…d assembly schema (fixes e2e_deployment schema mismatch)
…tion bundling to satisfy aws-cdk-lib 2.254 PathNotUnderRoot validation
…t local node_modules after aws-cdk CLI 2.1139 template change
soberm
approved these changes
Sep 1, 2026
Simone319
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Raises the
aws-cdk-libpeer dependency floor from^2.234.1to^2.254.0across all packages and refreshes the lockfile (now resolvesaws-cdk-libto2.267.0).Why
On Windows with recent Node.js releases, CDK asset fingerprinting crashes with
EINVALbecausefs.openSyncis invoked with theO_SYNC | O_DSYNCflag combination, which Node rejects on that platform. This makes the Windows unit/coverage job fully red while Linux and macOS stay green.The crash was fixed upstream in aws-cdk and first released in
aws-cdk-lib2.254.0. Bumping the floor to^2.254.0pulls in the fix.aws-cdk-lib2.254.0)What changed
aws-cdk-libfrom^2.234.1to^2.254.0in all 16packages/*/package.jsonfiles (peer/dep/devDep as applicable). No other dependencies changed.package-lock.json—aws-cdk-libnow resolves to2.267.0(latest within the range), deduped across the workspace.packages/create-amplify/src/default_packages.jsonso the defaultaws-cdk-libpin for new projects matches the lockfile (generated vianpm run update:create-amplify-deps).How tested
npm install+npm run build— clean.auth-construct,backend-storage,backend-data): 280/280.check:package-lock,check:package-json,check:api, and prettier all pass.The only local failures were in
platform-coreconfig/telemetry tests that write to a real user-profile path; these fail identically with and without this change in the local sandboxed environment (permission-restricted~path) and are unrelated to the CDK bump.