chore(deps): update pnpm to v8.6.3 #261

renovate · 2023-06-20T06:14:47Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`8.3.1` -> `8.6.3`

Release Notes

pnpm/pnpm

`v8.6.3`

Compare Source

Patch Changes

When running a script in multiple projects, the script outputs should preserve colours #2148.
Don't crash when the APPDATA env variable is not set on Windows #6659.
Don't fail when a package is archived in a tarball with malformed tar headers #5362.
Peer dependencies of subdependencies should be installed, when node-linker is set to hoisted #6680.
Throw a meaningful error when applying a patch to a dependency fails.
pnpm update --global --latest should work #3779.
pnpm license ls should work even when there is a patched git protocol dependency #6595

Our Gold Sponsors

Our Silver Sponsors

`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

`v8.5.1`

Compare Source

Patch Changes

Expanded missing command error, including 'did you mean' #6492.
When installation fails because the lockfile is not up-to-date with the package.json file(s), print out what are the differences #6536.
Normalize current working directory on Windows #6524.

Our Gold Sponsors

Our Silver Sponsors

`v8.5.0`

Compare Source

Minor Changes

pnpm patch-remove command added #6521.

Patch Changes

pnpm link -g <pkg-name> should not modify the package.json file #4341.
The deploy command should not ask for confirmation to purge the node_modules directory #6510.
Show cyclic workspace dependency details #5059.
Node.js range specified through the engines field should match prerelease versions #6509.

Our Gold Sponsors

Our Silver Sponsors

`v8.4.0`

Compare Source

Minor Changes

pnpm publish supports the --provenance CLI option #6435.

Patch Changes

Link the bin files of local workspace dependencies, when node-linker is set to hoisted 6486.
Ask the user to confirm the removal of node_modules directory unless the --force option is passed.
Do not create a node_modules folder with a .modules.yaml file if there are no dependencies inside node_modules.

Our Gold Sponsors

Our Silver Sponsors

Configuration

📅 Schedule: Branch creation - "after 9pm on sunday" (UTC), 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.

netlify · 2023-06-20T06:23:21Z