chore(deps): update pnpm to v11.15.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pnpm (source)	11.14.0 → 11.15.1

---

Release Notes

pnpm/pnpm (pnpm)

v11.15.1

Compare Source

v11.15.0: pnpm 11.15

Compare Source

Minor Changes

• Optional peer dependencies declared only via peerDependenciesMeta (for example debug's supports-color peer) are now resolved from a satisfying version already present in the dependency graph, the same way explicitly declared optional peer dependencies are. Previously such peers were only resolved this way when the package's metadata was read back from the lockfile, so an unrelated dependency change could rewrite peer resolutions across the whole lockfile.

Patch Changes

• Updated adm-zip to prevent crafted ZIP archives from causing excessive memory allocation.

• pnpm version -r no longer writes a versioning-ledger entry with no consumed intents as a bare intents: key, which the next run failed to read with ERR_PNPM_INVALID_VERSIONING_LEDGER. Empty intent lists are now written as intents: [], and the ledger reader accepts the bare form left by earlier releases.

• Fixed pnpr workspace resolution to preserve project names and versions for workspace: dependencies.

Platinum Sponsors

Gold Sponsors

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (1165 entries)...
✗ Lockfile failed supply-chain policy check (1165 entries in 7.3s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification:
  @nuxt/kit@4.5.0 was published at 2026-07-18T19:19:52.361Z, within the minimumReleaseAge cutoff (2026-07-18T00:36:15.133Z)
  @nuxt/nitro-server@4.5.0 was published at 2026-07-18T19:19:57.324Z, within the minimumReleaseAge cutoff (2026-07-18T00:36:15.133Z)
  @nuxt/schema@4.5.0 was published at 2026-07-18T19:20:19.481Z, within the minimumReleaseAge cutoff (2026-07-18T00:36:15.133Z)
  @nuxt/vite-builder@4.5.0 was published at 2026-07-18T19:20:24.348Z, within the minimumReleaseAge cutoff (2026-07-18T00:36:15.133Z)
  nuxt@4.5.0 was published at 2026-07-18T19:20:10.107Z, within the minimumReleaseAge cutoff (2026-07-18T00:36:15.133Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.