Skip to content

chore(deps): update pnpm to v7.28.0

Renovate Bot requested to merge renovate/pnpm-7.x into develop

This MR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 7.26.0 -> 7.28.0 age adoption passing confidence

Release Notes

pnpm/pnpm

v7.28.0

Compare Source

Minor Changes

  • Add --report-summary for pnpm exec and pnpm run #​6008.
  • Show path info for pnpm why --json or --long #​6103.
  • Extend the pnpm.peerDependencyRules.allowedVersions package.json option to support the parent>child selector syntax. This syntax allows for extending specific peerDependencies #​6108.

Patch Changes

  • Update the lockfile if a workspace has a new project with no dependencies.
  • Fix a case of installs not being deterministic and causing lockfile changes between repeat installs. When a dependency only declares peerDependenciesMeta and not peerDependencies, dependencies, or optionalDependencies, the dependency's peers were not considered deterministically before.
  • patch-commit should auto apply patches in workspaces #​6048
  • Automatically fix conflicts in v6 lockfile.
  • pnpm config set should write to the global config file by default #​5877.

Our Gold Sponsors

Our Silver Sponsors

v7.27.1

Compare Source

Patch Changes

  • Add store path description to the pnpm cli help.
  • Print a hint that suggests to run pnpm store prune, when a tarball integrity error happens.
  • Don't retry installation if the integrity checksum of a package failed and no lockfile was present.
  • Fail with a meaningful error message when cannot parse a proxy URL.
  • The strict-ssl, ca, key, and cert settings should work with HTTPS proxy servers #​4689.

Our Gold Sponsors

Our Silver Sponsors

v7.27.0

Compare Source

Minor Changes

  • A new resolution-mode added: lowest-direct. With this resolution mode direct dependencies will be resolved to their lowest versions. So if there is foo@^1.1.0 in the dependencies, then 1.1.0 will be installed, even if the latest version of foo is 1.2.0.
  • Support script selector with RegExp such as pnpm run /build:.*/ and execute the matched scripts with the RegExp #​5871.

Patch Changes

  • Fix version number replacing for namespaced workspace packages. workspace:@&#8203;foo/bar@* should be replaced with npm:@&#8203;foo/bar@<version> on publish #​6052.

  • When resolving dependencies, prefer versions that are already used in the root of the project. This is important to minimize the number of packages that will be nested during hoisting #​6054.

  • Deduplicate direct dependencies.

    Let's say there are two projects in the workspace that dependend on foo. One project has [email protected] in the dependencies while another one has foo@^1.0.0 in the dependencies. In this case, [email protected] should be installed to both projects as satisfies the version specs of both projects.

  • Use Map rather than Object in createPackageExtender to prevent read the prototype property to native function

Our Gold Sponsors

Our Silver Sponsors

v7.26.3

Compare Source

Patch Changes

  • Directories inside the virtual store should not contain the ( or ) chars. This is to fix issues with storybook and the new v6 pnpm-lock.yaml lockfile format #​5976.
  • The update command should not replace dependency versions specified via dist-tags #​5996.
  • Fixed an issue that was causing pnpm to stuck forever during installation #​5909.

Our Gold Sponsors

Our Silver Sponsors

v7.26.2

Compare Source

Patch Changes

  • Wrap text in pnpm audit output for better readability #​5981
  • Fix "cross-device link not permitted" error when node-linker is set to hoisted #​5992.

Our Gold Sponsors

Our Silver Sponsors

v7.26.1

Compare Source

Patch Changes

  • Fixed out of memory error that sometimes happens when node-linker is set to hoisted #​5988.
  • Fixed EMFILE: too many open files by using graceful-fs for reading bin files of dependencies #​5887.
  • Fix lockfile v6 on projects that use patched dependencies #​5967.

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Merge request reports