chore(deps): update pnpm to v8.6.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	8.5.1 -> 8.6.2
pnpm (source)	>=8.5.1 -> >=8.6.2

---

Release Notes

pnpm/pnpm

v8.6.2

Compare Source

Patch Changes

• Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly #​6648
• When patching a dependency, only consider files specified in the 'files' field of its package.json. Ignore all others #​6565
• Should always treat local file dependency as new dependency #​5381
• Output a warning message when "pnpm" or "resolutions" are configured in a non-root workspace project #​6636

Our Gold Sponsors

Our Silver Sponsors

v8.6.1

Compare Source

Patch Changes

• When dedupe-peer-dependents is enabled (default), use the path (not id) to determine compatibility.

  When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.

  Resolves: #​6605

• Some minor performance improvements by removing await from loops #​6617.

Our Gold Sponsors

Our Silver Sponsors

v8.6.0

Compare Source

Minor Changes

• Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.

  A new field will now be present in the lockfile: settings. It will store the values of two settings: autoInstallPeers and excludeLinksFromLockfile. If someone tries to perform a frozen-lockfile installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.

  The lockfile format version is bumped from v6.0 to v6.1.

  Related PR: #​6557
  Related issue: #​6312

• A new setting, exclude-links-from-lockfile, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.

  This setting was primarily added for use by Bit CLI, which links core aspects to node_modules from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.

Patch Changes

• Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks #​6544.
• When updating dependencies, preserve the range prefix in aliased dependencies. So npm:foo@1.0.0 becomes npm:foo@1.1.0.
• Print a meaningful error when a project referenced by the workspace: protocol is not found in the workspace #​4477.
• pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
• Peers resolution should not fail when a linked in dependency resolves a peer dependency.
• Build projects in a workspace in correct order #​6568.

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 these updates 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.

[codecov-commenter]

Codecov Report

Merging #720 (8e0d862) into main (c596260) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #720   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           45        45           
  Lines          681       681           
  Branches       133       133           
=========================================
  Hits           681       681