Update pnpm to v8.15.9

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	8.2.0 -> 8.15.9

---

Release Notes

pnpm/pnpm (pnpm)

v8.15.9: pnpm 8.15.9

Compare Source

Patch Changes

• Deduplicate bin names to prevent race condition and corrupted bin scripts #​7833.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.8

Compare Source

Patch Changes

• Upgrade tar to v6.2.1 in the dependences #​7939.
• If the script-shell option is configured to a .bat/.cmd file on Windows, pnpm will now error with ERR_PNPM_INVALID_SCRIPT_SHELL_WINDOWS. Newer versions of Node.js released in April 2024 do not support executing these files directly without behavior differences. If the script-shell option is necessary for your use-case, please set a .exe file instead.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.7

Compare Source

Patch Changes

• pnpm config get prints a comma-separated list for an array value instead of nothing.
• It should be possible to publish a tarball with custom dist-tag #​7845.
• Print the list of packages that were not built because they are ignored by configuration settings.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.6

Compare Source

Patch Changes

• The exit code of the child process should be preserved on pnpm run #​7817.
• When sorting packages in a workspace, take into account workspace dependencies specified as peerDependencies #​7813.
• Add --ignore-scripts argument to prune command #​7836.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v8.15.5

Compare Source

Patch Changes

• Correctly detect the active Node.js version during headless installation #​7801.
• The npm CLI executed from pnpm should not use Corepack #​7747.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.4

Compare Source

Patch Changes

• Print the right error code when a package fails to be added to the store #​7679.
• Don't fail on a tarball that appears to be not a USTAR or GNU TAR archive. Still try to unpack the tarball #​7120.
• Always add a name and version field to the index files in the store #​7115.
• Deleting a dependencies field via a readPackage hook should work #​7704.
• Symlinks should be resolved and uploaded to the side-effects cache #​7691.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.3

Compare Source

Patch Changes

• Remove vulnerable "ip" package from the dependencies #​7652.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.2

Compare Source

Patch Changes

• When purging multiple node_modules directories, pnpm will no longer print multiple prompts simultaneously.
• Don't print an unnecessary warning when adding new dependencies to a project that uses hoisted node_modules.
• Linking globally the command of a package that has no name in package.json #​4761.
• Installation should work with lockfile created by pnpm v9.0.0-alpha.4

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.1

Compare Source

Patch Changes

• Use the object-hash library instead of node-object-hash for hashing keys of side-effects cache #​7591.
• bundledDependencies should never be added to the lockfile with false as t

---

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.

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

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: dd5bff2

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.

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]

Someone is attempting to deploy a commit to a Personal Account owned by @X-oss-byte on Vercel.

@X-oss-byte first needs to authorize it.