fix(deps): update dependency pinia to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pinia (source)	^3.0.4 → ^4.0.0

---

Release Notes

vuejs/pinia (pinia)

v4.0.2

Compare Source

No significant changes

    View changes on GitHub

v4.0.1

Compare Source

   🐞 Bug Fixes

• Re-add missing types exports field  -  by @​rijkvanzanten in #​3154 (fb217)

    View changes on GitHub

v4.0.0

Compare Source

Pinia 4

Pinia 4 contains only technically breaking changes: ESM only and upgrading @vue/devtools-api which now must be installed alongside pinia. It contains a major refactor of errors and dev warnings with Nostics. They will ensure detected problems are easier to fix, both by humans and by agents.

   🚀 Features

• Upgrade devtools-api to v8  -  by @​posva (25572)
• Use nostics for better errors  -  by @​posva (f3522)
• Gracefully skip nullish values in storeToRefs  -  by @​JSap0914 and @​posva in #​3134 (cac82)
• Diagnostic on invalid properties when doing storeToRefs  -  by @​posva (e7313)
• Diagnostic wrong values in plugins  -  by @​posva (29835)
• Export piniaSymbol  -  by @​cexoso in #​2973 (d715b)

   🐞 Bug Fixes

• Use modern Object.hasOwn  -  by @​posva (57ecc)
• Respect skipHydrate marker on non-plain objects in shouldHydrate  -  by @​lestersg5hollis0 and Runecraft in #​3126 (2dcb3)
• Prevent duplicate watcher when same callback subscribed twice  -  by @​JSap0914 in #​3144 (99dca)
• ci: Pin pnpm to 11.7.0 to match action-setup bootstrap  -  by @​posva (d7973)
• devtools: Make settable getters (computed) editable  -  by @​posva in #​3151 (640b1)
• hmr: Preserve runtime-added properties of setup store refs  -  by @​chatman-media in #​3132 (aec2a)

    View changes on GitHub

---

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

? Verifying lockfile against supply-chain policies (1170 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        | [WARN] deprecated conventional-changelog-cli@5.0.0
Progress: resolved 254, reused 0, downloaded 0, added 0
Progress: resolved 415, reused 0, downloaded 1, added 0
Progress: resolved 584, reused 0, downloaded 1, added 0
Progress: resolved 757, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (1170 entries in 5.1s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification:
  @intlify/core-base@11.4.7 was published at 2026-07-20T12:17:48.918Z, within the minimumReleaseAge cutoff (2026-07-20T05:31:05.488Z)
  @intlify/devtools-types@11.4.7 was published at 2026-07-20T12:17:53.129Z, within the minimumReleaseAge cutoff (2026-07-20T05:31:05.488Z)
  @intlify/message-compiler@11.4.7 was published at 2026-07-20T12:17:57.178Z, within the minimumReleaseAge cutoff (2026-07-20T05:31:05.488Z)
  @intlify/shared@11.4.7 was published at 2026-07-20T12:18:05.951Z, within the minimumReleaseAge cutoff (2026-07-20T05:31:05.488Z)
  vue-i18n@11.4.7 was published at 2026-07-20T12:18:10.681Z, within the minimumReleaseAge cutoff (2026-07-20T05:31:05.488Z)

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.