Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
"docker-build": "docker build -t fresco:latest ."
},
"dependencies": {
"@aws-sdk/client-s3": "^3.1068.0",
"@aws-sdk/client-s3": "^3.1086.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Bump the S3 presigner with the client

With this bump the lockfile now installs @aws-sdk/client-s3@3.1086.0 against @smithy/core@3.29.3, while @aws-sdk/s3-request-presigner stays on 3.1068.0 and is locked to @smithy/core@3.24.7. In the S3 upload/download paths that call getSignedUrl(client, new PutObjectCommand/GetObjectCommand(...)), those duplicated Smithy core types make the client/command incompatible during pnpm typecheck (which the build workflow runs), so this dependency-only change can fail CI. Please bump @aws-sdk/s3-request-presigner in lockstep with the S3 client.

Useful? React with 👍 / 👎.

"@aws-sdk/s3-request-presigner": "^3.1068.0",
"@base-ui/react": "^1.5.0",
"@codaco/fresco-ui": "^3.0.1",
Expand Down
Loading
Loading