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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this bump the lockfile now installs
@aws-sdk/client-s3@3.1086.0against@smithy/core@3.29.3, while@aws-sdk/s3-request-presignerstays on 3.1068.0 and is locked to@smithy/core@3.24.7. In the S3 upload/download paths that callgetSignedUrl(client, new PutObjectCommand/GetObjectCommand(...)), those duplicated Smithy core types make the client/command incompatible duringpnpm typecheck(which the build workflow runs), so this dependency-only change can fail CI. Please bump@aws-sdk/s3-request-presignerin lockstep with the S3 client.Useful? React with 👍 / 👎.