Update pnpm to v7.30.3

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	7.29.0 -> 7.30.3

---

Release Notes

pnpm/pnpm

### [`v7.30.3`](https://togithub.com/pnpm/pnpm/releases/tag/v7.30.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.30.2...v7.30.3) #### Patch Changes - Should use most specific override rule when multiple rules match the same target [#​6210](https://togithub.com/pnpm/pnpm/issues/6210). - Fix regression introduced in v7.30.1 [#​6271](https://togithub.com/pnpm/pnpm/issues/6271). #### Our Gold Sponsors #### Our Silver Sponsors ### [`v7.30.2`](https://togithub.com/pnpm/pnpm/compare/v7.30.1...v7.30.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.30.1...v7.30.2) ### [`v7.30.1`](https://togithub.com/pnpm/pnpm/releases/tag/v7.30.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.30.0...v7.30.1) #### Patch Changes - Don't write the `pnpm-lock.yaml` file if it has no changes and `pnpm install --frozen-lockfile` was executed [#​6158](https://togithub.com/pnpm/pnpm/issues/6158). - Fix git-hosted dependencies referenced via `git+ssh` that use semver selectors [#​6239](https://togithub.com/pnpm/pnpm/pull/6239). - When publish some package throws an error, the exit code should be non-zero [#​5528](https://togithub.com/pnpm/pnpm/issues/5528). - Only three paths are displayed in `pnpm audit` output [#​6203](https://togithub.com/pnpm/pnpm/issues/6203) - Aliased packages should be used to resolve peer dependencies too [#​4301](https://togithub.com/pnpm/pnpm/issues/4301). #### Our Gold Sponsors #### Our Silver Sponsors ### [`v7.30.0`](https://togithub.com/pnpm/pnpm/releases/tag/v7.30.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.29.3...v7.30.0) ##### Minor Changes - Allow to set a custom directory for storing patch files via the `patches-dir` setting [#​6215](https://togithub.com/pnpm/pnpm/pull/6215) ##### Patch Changes - New directories should be prepended to NODE_PATH in command shims, not appended. - Retry copying file on EBUSY error [#​6201](https://togithub.com/pnpm/pnpm/issues/6201). ##### Our Gold Sponsors ##### Our Silver Sponsors ### [`v7.29.3`](https://togithub.com/pnpm/pnpm/releases/tag/v7.29.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.29.2...v7.29.3) #### Patch Changes - Command shim should not set higher priority to the `node_modules/.pnpm/node_modules` directory through the `NODE_PATH` env variable, then the command's own `node_modules` directory [#​5176](https://togithub.com/pnpm/pnpm/issues/5176). - `extend-node-path` is set back to `true` by default. It was set to `false` in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extending `NODE_PATH`. We have fixed the Jest issue with a different solution [#​6213](https://togithub.com/pnpm/pnpm/issues/6213). #### Our Gold Sponsors #### Our Silver Sponsors ### [`v7.29.2`](https://togithub.com/pnpm/pnpm/compare/v7.29.1...v7.29.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.29.1...v7.29.2) ### [`v7.29.1`](https://togithub.com/pnpm/pnpm/releases/tag/v7.29.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v7.29.0...v7.29.1) #### Patch Changes - Settings related to authorization should be set/deleted by npm CLI [#​6181](https://togithub.com/pnpm/pnpm/issues/6181). #### 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.

[renovate[bot]]

⚠ 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

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit