chore(deps): update dependency pinia to v3

[wajeht-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pinia (source)	^2.1.7 → ^3.0.0

---

Release Notes

vuejs/pinia (pinia)

v3.0.4

Compare Source

Please refer to CHANGELOG.md for details.

v3.0.3

Compare Source

Please refer to CHANGELOG.md for details.

v3.0.2

Please refer to CHANGELOG.md for details.

v3.0.0: Pinia 3.0

Compare Source

This version of Pinia has no new features, it drops support for Vue 2 and other deprecated APIs. It should be an straightforward upgrade for most users! 🎉

See the migration guide for help.

⚠ BREAKING CHANGES

• We now use the native Awaited introduced in TS 4.5, so you need at least TS 4.5 to use Pinia 3.0. That being said, it's always better to have an up to date version of TS.
• PiniaStorePlugin is now removed. Use PiniaPlugin instead.
• defineStore({ id: 'id' }) is now removed. Use defineStore('id') instead
• Pinia is now published as a type: module package but it still provides CJS versions dist files

Please refer to CHANGELOG.md for details.

---

Configuration

📅 Schedule: Branch creation - "after 12am and before 8am every weekday,every weekend" in timezone America/Chicago, 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 has been generated by Renovate Bot.

[wajeht-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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: pinia-plugin-persistedstate@3.2.1
npm ERR! Found: pinia@3.0.4
npm ERR! node_modules/pinia
npm ERR!   pinia@"^3.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer pinia@"^2.0.0" from pinia-plugin-persistedstate@3.2.1
npm ERR! node_modules/pinia-plugin-persistedstate
npm ERR!   pinia-plugin-persistedstate@"^3.2.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: pinia@2.3.1
npm ERR! node_modules/pinia
npm ERR!   peer pinia@"^2.0.0" from pinia-plugin-persistedstate@3.2.1
npm ERR!   node_modules/pinia-plugin-persistedstate
npm ERR!     pinia-plugin-persistedstate@"^3.2.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2026-02-22T04_04_02_176Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-02-22T04_04_02_176Z-debug-0.log