chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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

---

Configuration

📅 Schedule: (in timezone America/Vancouver)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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.

---

Thanks for the PR!

Deployments, as required, will be available below:
Any successful deployments (not always required) will be available here

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

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

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: vue-router@5.1.0
npm error Found: vite@5.4.21
npm error node_modules/vite
npm error   dev vite@"^5.4.10" from the root project
npm error   peer vite@"^5.0.0 || ^6.0.0" from @vitejs/plugin-vue@5.2.4
npm error   node_modules/@vitejs/plugin-vue
npm error     dev @vitejs/plugin-vue@"^5.2.1" from the root project
npm error   4 more (vitest, vite-plugin-istanbul, @vitest/mocker, vite-node)
npm error
npm error Could not resolve dependency:
npm error peerOptional vite@"^7.0.0 || ^8.0.0" from vue-router@5.1.0
npm error node_modules/vue-router
npm error   vue-router@"^5.0.4" from the root project
npm error
npm error Conflicting peer dependency: vite@8.0.16
npm error node_modules/vite
npm error   peerOptional vite@"^7.0.0 || ^8.0.0" from vue-router@5.1.0
npm error   node_modules/vue-router
npm error     vue-router@"^5.0.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-17T22_25_43_155Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-17T22_25_43_155Z-debug-0.log

[github-actions]

There is no coverage information present for the Files changed

[github-actions]

There is no coverage information present for the Files changed

[github-actions]

There is no coverage information present for the Files changed