refactor: Bump @aws-sdk/lib-storage and @aws-sdk/client-s3 to 3.1091.0

[mtrezza]

Closes #573

This co-bumps @aws-sdk/client-s3 alongside @aws-sdk/lib-storage (both from 3.1032.0 to 3.1091.0).

Bumping @aws-sdk/lib-storage alone (as in #573) breaks npm ci: lib-storage 3.109x declares a peer dependency on @aws-sdk/client-s3 ^3.109x, which is not satisfied while client-s3 is pinned at 3.1032.0. Bumping both to the same version satisfies the peer requirement and restores a clean install.

Verified locally: npm ci exits 0 with the updated lockfile (no ERESOLVE, no --legacy-peer-deps).

Summary by CodeRabbit

• Bug Fixes
  • Updated AWS S3 integration packages to newer patch versions.
  • Refreshed related AWS SDK and supporting library components for improved compatibility and reliability.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: af28c5e9-25e3-4ade-a11f-ffcc0db7f800

📥 Commits

Reviewing files that changed from the base of the PR and between dfdedf4 and 2bf4f5e.

📒 Files selected for processing (2)

• package-lock.json
• package.json

---

📝 Walkthrough

Walkthrough

The S3 adapter upgrades @aws-sdk/client-s3 and @aws-sdk/lib-storage from 3.1032.0 to 3.1091.0, with corresponding AWS SDK and Smithy lockfile updates.

Changes

AWS SDK dependency refresh

Layer / File(s)	Summary
Direct S3 dependency versions package.json, package-lock.json	Updates the direct S3 package pins and aligns @aws-sdk/lib-storage’s peer dependency on @aws-sdk/client-s3.
Transitive AWS SDK graph package-lock.json	Refreshes credential providers, middleware, signing utilities, XML support, Smithy HTTP and credential packages, and removes superseded utility entries.

Estimated code review effort: 2 (Simple) | ~10 minutes

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	❓ Inconclusive	Repo only shows dependency bumps; no review-thread or discussion artifacts are present, so feedback engagement can't be verified.	Provide the PR review comments or conversation history showing the author discussed feedback and either implemented it or got it retracted.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the change set and uses an allowed prefix with a capitalized action word.
Linked Issues check	✅ Passed	The PR upgrades @aws-sdk/lib-storage to 3.1091.0 and updates the related package.json and lockfile entries as required by #573.
Out of Scope Changes check	✅ Passed	The changes stay within the AWS SDK version bump and lockfile refresh needed for the linked issue.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	PASS: metadata-only AWS SDK bump; advisory review found no introduced vulnerable pattern, and checked transitive advisories are outside their affected ranges.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.77%. Comparing base (dfdedf4) to head (2bf4f5e).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #580   +/-   ##
=======================================
  Coverage   97.77%   97.77%           
=======================================
  Files           2        2           
  Lines         225      225           
=======================================
  Hits          220      220           
  Misses          5        5           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.