chore(deps): update pnpm to v10.6.4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	10.6.2 -> 10.6.4

---

Release Notes

pnpm/pnpm (pnpm)

v10.6.4: pnpm 10.6.4

Compare Source

Patch Changes

• Fix pnpm dlx with --allow-build flag #​9263.
• Invalid Node.js version in use-node-version should not cause pnpm itself to break #​9276.
• The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #​9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

Platinum Sponsors

Gold Sponsors

v10.6.3

Compare Source

Patch Changes

• pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #​9233. This fixes regression introduced via #​9211.

• Add the missing node-options config to recursive run #​9180.

• Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

  See details in #​9259.

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e676030

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
zag-nextjs	✅ Ready (Inspect)	Visit Preview	Mar 17, 2025 3:41pm
zag-solid	✅ Ready (Inspect)	Visit Preview	Mar 17, 2025 3:41pm
zag-svelte	✅ Ready (Inspect)	Visit Preview	Mar 17, 2025 3:41pm
zag-vue	✅ Ready (Inspect)	Visit Preview	Mar 17, 2025 3:41pm
zag-website	✅ Ready (Inspect)	Visit Preview	Mar 17, 2025 3:41pm