chore(deps): update pnpm.catalog.default unplugin-vue-components to v32

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
unplugin-vue-components	^31.0.0 → ^32.1.0

---

Release Notes

unplugin/unplugin-vue-components (unplugin-vue-components)

v32.1.0

Compare Source

No significant changes

    View changes on GitHub

v32.0.0

Compare Source

   🚨 Breaking Changes

• Upgrade unplugin to v3  -  by @​antfu (f147e)

    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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8b05352

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[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

Scope: all 9 workspace projects
? Verifying lockfile against supply-chain policies (1394 entries)...
[WARN] The metadata of xlsx is missing the "time" field; skipping the minimumReleaseAge check for this package.
✗ Lockfile failed supply-chain policy check (1394 entries in 11.8s)
[ERR_PNPM_TRUST_DOWNGRADE] 6 lockfile entries failed verification:
  chokidar@4.0.3 High-risk trust downgrade for "chokidar@4.0.3" (possible package takeover)
  semver@5.7.2 High-risk trust downgrade for "semver@5.7.2" (possible package takeover)
  semver@6.3.1 High-risk trust downgrade for "semver@6.3.1" (possible package takeover)
  undici-types@6.21.0 High-risk trust downgrade for "undici-types@6.21.0" (possible package takeover)
  vite@5.4.21 High-risk trust downgrade for "vite@5.4.21" (possible package takeover)
  xlsx@0.20.3 Missing time for version 0.20.3 of xlsx in metadata

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.