chore(deps): update dependency immer to v11.1.15

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
immer	11.1.8 → 11.1.15

---

Release Notes

immerjs/immer (immer)

v11.1.15

Compare Source

Bug Fixes

• correct curried produceWithPatches return type (#​1249) (a3be9df), closes #​1045

v11.1.14

Compare Source

Bug Fixes

• throw proper immer error when applyPatches path traverses null (#​1251) (e38ad71)

v11.1.13

Compare Source

Bug Fixes

• draft relocated base refs after reverse/sort in array-methods plugin (#​1255) (a73672a)

v11.1.12

Compare Source

Bug Fixes

• Revert "prevent prototype pollution via constructor.prototype access (CVE-2026-XXXX) (#​1259)" (#​1271) (4d3d6ff), closes #​1266 #​1268 #​1265

v11.1.11

Compare Source

Bug Fixes

• improve DraftMap.{entries,values}() compatibility#​1228 (#​1228) (858d036)

v11.1.10

Compare Source

Bug Fixes

• undefined assigned to a prototype-inherited key gets dropped (#​1262) (16e225b)

v11.1.9

Compare Source

Bug Fixes

• prevent prototype pollution via constructor.prototype access (CVE-2026-XXXX) (#​1259) (48fc378)

---

Configuration

📅 Schedule: (UTC)

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

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

♻ 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

Scope: all 8 workspace projects
? Verifying lockfile against supply-chain policies (749 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 37, reused 0, downloaded 0, added 0
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 52, reused 0, downloaded 0, added 0
Progress: resolved 55, reused 0, downloaded 0, added 0
Progress: resolved 59, reused 0, downloaded 0, added 0
Progress: resolved 66, reused 0, downloaded 0, added 0
Progress: resolved 228, reused 0, downloaded 0, added 0
Progress: resolved 374, reused 0, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (749 entries in 9.3s)
Progress: resolved 381, reused 0, downloaded 0, added 0
Progress: resolved 386, reused 0, downloaded 0, added 0
Progress: resolved 404, reused 0, downloaded 0, added 0
Progress: resolved 619, reused 0, downloaded 0, added 0
Progress: resolved 749, reused 0, downloaded 0, added 0
[ERR_PNPM_STRICT_MIN_RELEASE_AGE_REQUIRES_SAVE] minimumReleaseAgeStrict cannot be combined with --no-save: approval would require writing to minimumReleaseAgeExclude in pnpm-workspace.yaml, which --no-save prevents.

Drop --no-save so the exclude list can be persisted, or set minimumReleaseAgeStrict: false to let the install proceed without prompting (the lockfile would still trigger the auto-collect on the next normal install).