Update vulnerable JS dependencies in the pnpm lockfile - #5630

Fixes

Supersedes #5569, #5558, #5553, #5535, #5533, #5531, #5530 and #5511.

Description

Applies the dependency updates that Renovate's open [SECURITY] PRs were supposed to make. Those PRs all carry an identical lockfile diff that leaves the vulnerable versions in place, because the Renovate version in use updates pnpm lockfiles without --recursive (see #5628 for the fix to Renovate itself).

Nuxt (#5534) is deliberately left at 3.15.1. Nuxt 3.17 and later move to unhead v2 and a newer nitropack, which breaks type checking in nuxt.config.ts, app.vue, error.vue and the pages that still pass hid to useHead. That upgrade needs code changes and its own PR, and should target at least 3.21.10 since newer Nuxt advisories (GHSA-934w-87qh-qr26, GHSA-c9cv-mq2m-ppp3, GHSA-9pgf-384g-p7mv) are fixed there rather than in 3.19.0.

The only package.json change is the root pnpm.overrides range for vite, which moves from ^6.0.11 to ^6.4.1. Without it the frontend's transitive vite resolution stays at 6.0.11 even after the update.

Generated with the repository's pinned pnpm 10.2.0:

pnpm update -r --no-save js-yaml@4.1.1 axios@1.13.5 rollup@4.59.0 vite@6.4.1 glob@11.1.0 @intlify/core@11.1.10 @intlify/core-base@11.1.10 vue-i18n@11.1.10 --lockfile-only
pnpm dedupe --lockfile-only

Testing Instructions

CI covers this. To confirm the lockfile no longer contains the vulnerable versions:

grep -cE "^  '?(axios@1\.8\.2|js-yaml@4\.1\.0|vite@6\.0\.11|rollup@4\.31\.0|glob@11\.0\.0|vue-i18n@11\.1\.2|@intlify/core(-base)?@11\.0\.1)[:(]" pnpm-lock.yaml

should print 0.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
  PRs) or the media properties generator (ov just catalog/generate-docs media-props
  for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

🤖 Generated with Claude Code