chore(deps): update pnpm to v8.15.9 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	8.15.4 -> 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

---

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 is behind base branch, 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

[18:30:47.740] INFO (239): Installing npm [email protected]...
[18:30:49.147] WARN (239): Npm error:
npm info using [email protected]
npm info using [email protected]
npm http fetch GET 404 https://registry.npmjs.org/pnpm 207ms (cache skip)
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/pnpm - Not found
npm error 404
npm error 404  '[email protected]' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /tmp/containerbase-npm-IMkXo8/_logs/2024-12-08T18_30_48_081Z-debug-0.log
[18:30:49.168] ERROR (239): npm install command failed
[18:30:49.169] FATAL (239): Install tool pnpm failed in 1.4s.