chore(deps): update all non-major dependencies to ^3.5.38

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vue (source)	^3.5.37 → ^3.5.38

---

Release Notes

vuejs/core (vue)

v3.5.38

Compare Source

---

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 (180 entries)...
✗ Lockfile failed supply-chain policy check (180 entries in 2.1s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification:
  @vue/compiler-core@3.5.37 was published at 2026-06-11T05:06:26.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/compiler-dom@3.5.37 was published at 2026-06-11T05:06:34.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/compiler-sfc@3.5.37 was published at 2026-06-11T05:06:40.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/compiler-ssr@3.5.37 was published at 2026-06-11T05:06:46.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/reactivity@3.5.37 was published at 2026-06-11T05:06:50.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/runtime-core@3.5.37 was published at 2026-06-11T05:06:55.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/runtime-dom@3.5.37 was published at 2026-06-11T05:06:59.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/server-renderer@3.5.37 was published at 2026-06-11T05:07:03.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  @vue/shared@3.5.37 was published at 2026-06-11T05:07:09.000Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)
  vue@3.5.37 was published at 2026-06-11T05:15:41.734Z, within the minimumReleaseAge cutoff (2026-06-10T12:10:53.556Z)

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.