chore(deps): update all non-major dependencies (v3)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxthub/core (source)	^0.8.19 -> ^0.8.21
pnpm (source)	10.6.5 -> 10.7.0

---

Release Notes

nuxt-hub/core (@​nuxthub/core)

v0.8.21

Compare Source

compare changes

🩹 Fixes

• Typo safe-buffer -> safer-buffer (e09663b)

❤️ Contributors

• Sébastien Chopin (@​atinux)

v0.8.20

Compare Source

compare changes

🚀 Enhancements

• Send file mime to multi-part upload (#​518)

🏡 Chore

• Add alias for safe-buffer to node:buffer (39bc7ec)

❤️ Contributors

• Farnabaz [email protected]
• Sébastien Chopin (@​atinux)

pnpm/pnpm (pnpm)

v10.7.0

Compare Source

Minor Changes

• pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

• It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

• Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

  For example:

  patchedDependencies:
    foo: patches/foo-1.patch
    foo@^2.0.0: patches/foo-2.patch
    [email protected]: patches/foo-3.patch

  The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

  [!WARNING]
  The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

  # pnpm-workspace.yaml
  patchedDependencies:
    # the specialized sub range
    '[email protected]': patches/foo.2.2.0-2.8.0.patch
    # the more general patch, excluding the sub range above
    'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

  In most cases, however, it's sufficient to just define an exact version to override the range.

• pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

• Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

• Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

  If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

  If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

  If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

• Remove dependency paths from audit output to prevent out-of-memory errors #​9280.

---

Configuration

📅 Schedule: 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.

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

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@3695

commit: 97a19ad

[nuxthub-admin]

✅ Deployed ui3

Deployed ui3 97a19ad to preview

🔗	renovate-v3-all-minor-patch.ui-6q2.pages.dev
📌	27e1bcaf.ui-6q2.pages.dev
📱	View QR Code

📋 View deployment logs