chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • Between 12:00 AM and 05:59 AM, only on Monday (* 0-5 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

---

Note

Medium Risk
Touches the full AWS S3 client and signing stack used by packages/storage, so regressions in uploads, presigning, or auth are possible despite staying on existing semver ranges.

Overview
Refreshes pnpm-lock.yaml only (Renovate lock file maintenance). No package.json manifest changes—updates are resolved versions within existing semver ranges.

packages/storage and shared pick up newer AWS SDK v3 builds: @aws-sdk/client-s3 and related S3 packages move 3.1073.0 → 3.1078.0, with matching bumps across credential providers, @aws-sdk/core, @smithy/*, and @smithy/signature-v4 (5.5.1 → 5.6.1). The lockfile’s S3 client graph is slimmer (e.g. @aws-sdk/checksums wired directly into client-s3, fewer standalone @aws-crypto/* and XML parser entries).

Root dev tooling resolves publint 0.3.21 and postcss 8.5.16, which flows through tsup and vite peer chains.

^{Reviewed by Cursor Bugbot for commit 2c63ffa. Bugbot is set up for automated code reviews on this repo. Configure here.}