chore(deps): update pnpm to v8.6.11

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`8.6.10` -> `8.6.11`

Release Notes

pnpm/pnpm (pnpm)

### [`v8.6.11`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.11) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.10...v8.6.11) #### Patch Changes - Change the install error message when a lockfile is wanted but absent to indicate the wanted lockfile is absent, not present. This now reflects the actual error [#6851](https://togithub.com/pnpm/pnpm/pull/6851). - When dealing with a local dependency that is a path to a symlink, a new symlink should be created to the original symlink, not to the actual directory location. - The length of the temporary file names in the content-addressable store reduced in order to prevent `ENAMETOOLONG` errors from happening [#6842](https://togithub.com/pnpm/pnpm/issues/6842). - Don't print "added" stats, when installing with `--lockfile-only`. - Installation of a git-hosted dependency should not fail if the `pnpm-lock.yaml` file of the installed dependency is not up-to-date [#6865](https://togithub.com/pnpm/pnpm/issues/6865). - Don't ignore empty strings in params [#6594](https://togithub.com/pnpm/pnpm/issues/6594). - Always set `dedupe-peer-dependents` to `false`, when running installation during deploy [#6858](https://togithub.com/pnpm/pnpm/issues/6858). - When several containers use the same store simultaneously, there's a chance that multiple containers may create a temporary file at the same time. In such scenarios, pnpm could fail to rename the temporary file in one of the containers. This issue has been addressed: pnpm will no longer fail if the temporary file is absent but the destination file exists. - Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) [#6863](https://togithub.com/pnpm/pnpm/pull/6864). #### Our 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 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 has been generated by Mend Renovate. View repository job log here.

hairyf / vue3-pixi

chore(deps): update pnpm to v8.6.11 #37

Release Notes

Configuration