Update pnpm to v7.13.2 #21

renovate · 2022-08-23T10:29:59Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`7.9.3` -> `7.13.2`

Release Notes

pnpm/pnpm

`v7.13.2`

Compare Source

Patch Changes

When linking commands to a directory, remove any .exe files that are already present in that target directory by the same name.

This fixes an issue with pnpm global update on Windows. If pnpm was installed with the standalone script and then updated with pnpm using pnpm add --global pnpm, the exe file initially created by the standalone script should be removed.
When a direct dependency fails to resolve, print the path to the project directory in the error message.
pnpm patch-commit should work when the patch directory is specified with a trailing slash #5449.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.1`

Compare Source

Patch Changes

pnpm update --interactive should not list dependencies ignored via the pnpm.updateConfig.ignoreDependencies setting.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.0`

Compare Source

Minor Changes

Ignore packages listed in package.json > pnpm.updateConfig.ignoreDependencies fields on update/outdated command #5358

For instance, if you don't want webpack automatically to be updated when you run pnpm update --latest, put this to your package.json:
```
{
  "pnpm": {
    "updateConfig": {
      "ignoreDependencies": ["webpack"]
    }
  }
}
```
Patterns are also supported, so you may ignore for instance any packages from a scope: @babel/*.
It is possible now to update all dependencies except the listed ones using !. For instance, update all dependencies, except lodash:
```
  pnpm update !lodash
```
It also works with pattends, for instance:
```
  pnpm update !@&#8203;babel/*
```
And it may be combined with other patterns:
```
  pnpm update @&#8203;babel/* !@&#8203;babel/core
```

Patch Changes

Hooks should be applied on pnpm deploy #5306.
Stop --filter-prod option to run command on all the projects when used on workspace. --filter-prod option now only filter from dependencies and omit devDependencies instead of including all the packages when used on workspace. So what was happening is that if you use --filter-prod on workspace root like this:
```
pnpm --filter-prod ...build-modules exec node -e 'console.log(require(`./package.json`).name)'
```
it was printing all the package of workspace, where it should only print the package name of itself and packages where it has been added as dependency (not as devDependencies)
Don't override the root dependency when auto installing peer dependencies #5412.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

GitHub Workflows security hardening by @sashashuhttps://github.com/pnpm/pnpm/pull/5405l/5405
feat: merge readPackage hook from opts and pnpmfile by @AGrzhttps://github.com/pnpm/pnpm/pull/5403l/5403
feat: excluding deps from update by @zkochhttps://github.com/pnpm/pnpm/pull/5432l/5432
fix: dir path repeated join in link global by @lvhttps://github.com/pnpm/pnpm/pull/5434l/5434
fix: filter-prod flag including all workspace pkgs by @noorulhhttps://github.com/pnpm/pnpm/pull/5437l/5437
Feature: ignore packages listed in package.json > pnpm.updateConfig.ignoreDependencies on update/outdated commands by @Shinyaigehttps://github.com/pnpm/pnpm/pull/5408l/5408
fix: don't override root deps when auto installing peers by @zkochhttps://github.com/pnpm/pnpm/pull/5442l/5442

New Contributors

@sashashura made their first contributihttps://github.com/pnpm/pnpm/pull/5405l/5405
@AGrzes made their first contributihttps://github.com/pnpm/pnpm/pull/5403l/5403
@noorulh06 made their first contributihttps://github.com/pnpm/pnpm/pull/5437l/5437

Full Changelog: pnpm/pnpm@v7.12.2...v7.13.0

`v7.12.2`

Compare Source

Patch Changes

Don't crash when auto-install-peers is true and the project has many complex circular dependencies #5394.
pnpm link --global should work with the --dir=<path> option #5371.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

fix: error in pnpm --dir link --global by @lvhttps://github.com/pnpm/pnpm/pull/5371l/5371
fix: cli crash with auto-install-peers=true by @zkochhttps://github.com/pnpm/pnpm/pull/5394l/5394

New Contributors

@lvqq made their first contributihttps://github.com/pnpm/pnpm/pull/5371l/5371

Full Changelog: pnpm/pnpm@v7.12.1...v7.12.2

`v7.12.1`

Compare Source

Patch Changes

Deduplicate peer dependencies when automatically installing them #5373.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

fix: deduplicate peer deps by @zkochhttps://github.com/pnpm/pnpm/pull/5377l/5377

Full Changelog: pnpm/pnpm@v7.12.0...v7.12.1

`v7.12.0`

Compare Source

Minor Changes

A new setting supported in the pnpm section of the package.json file: allowNonAppliedPatches. When it is set to true, non-applied patches will not cause an error, just a warning will be printed. For example:

{
  "name": "foo",
  "version": "1.0.0",
  "pnpm": {
    "patchedDependencies": {
      "express@4.18.1": "patches/express@4.18.1.patch"
    },
    "allowNonAppliedPatches": true
  }
}

Now it is possible to exclude packages from hoisting by prepending a ! to the pattern. This works with both the hoist-pattern and public-hoist-pattern settings. For instance:
```
public-hoist-pattern[]='*types*'
public-hoist-pattern[]='!@&#8203;types/react'

hoist-pattern[]='*eslint*'
hoist-pattern[]='!*eslint-plugin*'
```
Ref #5272

Patch Changes

When the same dependency with missing peers is used in multiple workspace projects, install the missing peers in each workspace project #4820.
pnpm patch should work on files that don't have an end of line #5320.
Fix pnpm patch using a custom --edit-dir.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

fix(patch): allow to edit a package in any directory by @zkochhttps://github.com/pnpm/pnpm/pull/5331l/5331
feat(matcher): ignore patterns by @LuciNyhttps://github.com/pnpm/pnpm/pull/5336l/5336
fix(patch): ignore No newline at end of file by @await-ohttps://github.com/pnpm/pnpm/pull/5321l/5321
feat(patch): allow non-applied patches by @larrybahr-ocelhttps://github.com/pnpm/pnpm/pull/5354l/5354
chore: update @pnpm/meta-updater by @ibehttps://github.com/pnpm/pnpm/pull/5360pm/pull/5360
fix: auto-install-peers in a workspace by @zkochhttps://github.com/pnpm/pnpm/pull/5359l/5359

New Contributors

@await-ovo made their first contributihttps://github.com/pnpm/pnpm/pull/5321l/5321
@larrybahr-ocelot made their first contributihttps://github.com/pnpm/pnpm/pull/5354l/5354

Full Changelog: pnpm/pnpm@v7.11.0...v7.12.0

`v7.11.0`

Compare Source

Minor Changes

pnpm patch: edit the patched package in a directory specified by the --edit-dir option. E.g., pnpm patch express@3.1.0 --edit-dir=/home/xxx/src/patched-express #5304

Patch Changes

Auto installing a peer dependency in a workspace that also has it as a dev dependency in another project #5144.
When an error happens during installation of a subdependency, print some context information in order to be able to locate that subdependency. Print the exact chain of packages that led to the problematic dependency.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

feat(plugin-command-patching): add path option to patch command by @roseline1https://github.com/pnpm/pnpm/pull/5304l/5304
fix: improve dependency installation error message by @zkochhttps://github.com/pnpm/pnpm/pull/5247l/5247
fix: auto installing peer dep in a workspace by @zkochhttps://github.com/pnpm/pnpm/pull/5307l/5307

New Contributors

@roseline124 made their first contributihttps://github.com/pnpm/pnpm/pull/5304l/5304

Full Changelog: pnpm/pnpm@v7.10.0...v7.11.0

`v7.10.0`

Compare Source

Minor Changes

New time-based resolution strategy supported.

When resolution-mode is set to time-based, pnpm will resolve dependencies the following way:
1. 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.
2. Subdependencies will be resolved from versions that were published before the last direct dependency was published.
With this resolution mode installations with hot cache are faster. It also reduces the chance of subdependency hijacking as subdependencies will be updated only if direct dependencies are updated.

This resolution mode works only with npm's full metadata. So it is slower in some scenarios. However, if you use Verdaccio v5.15.1 or newer, you may set the registry-supports-time-field setting to true, and it will be really fast.

Related RFC.
Enhance pnpm env with the remove command. To remove a Node.js version installed by pnpm, run:
```
pnpm env remove --global <node.js version>
```

Patch Changes

pnpm store prune should remove all cached metadata.
Don't modify the manifest of the injected workspace project, when it has the same dependency in prod and peer dependencies.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

test: fix NODE_PATH test on Windows by @zkochhttps://github.com/pnpm/pnpm/pull/5257l/5257
refactor: resolve dependencies by @zkochhttps://github.com/pnpm/pnpm/pull/5267l/5267
feat(env): add remove command to pnpm env by @mark-omarhttps://github.com/pnpm/pnpm/pull/5263l/5263
docs(CONTRIBUTING): correct setup instructions for first-time clone by @gwhitnhttps://github.com/pnpm/pnpm/pull/5289l/5289
fix: don't modify the injected project's manifest by @zkochhttps://github.com/pnpm/pnpm/pull/5294l/5294
feat: time-based resolution mode by @zkochhttps://github.com/pnpm/pnpm/pull/5238l/5238
feat: resolve direct deps to lowest version when resolution-mode is time-based by @zkochhttps://github.com/pnpm/pnpm/pull/5298l/5298
fix: add fallback for time-based resolution by @zkochhttps://github.com/pnpm/pnpm/pull/5302l/5302

New Contributors

@mark-omarov made their first contributihttps://github.com/pnpm/pnpm/pull/5263l/5263
@gwhitney made their first contributihttps://github.com/pnpm/pnpm/pull/5289l/5289

Full Changelog: pnpm/pnpm@v7.9.5...v7.10.0

`v7.9.5`

Compare Source

Patch Changes

Set NODE_PATH when prefer-symlinked-executables is enabled #5251.
Fail with a meaningful error when the audit endpoint doesn't exist #5200.
Symlink a local dependency to node_modules, even if the target directory doesn't exist #5219.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Fix pnpm audit bad API response on private registry by @timtong19https://github.com/pnpm/pnpm/pull/5246l/5246
fix: set NODE_PATH when is turned on by @d3https://github.com/pnpm/pnpm/pull/5251l/5251
fix: symlink local dep even when target dir does not exist by @zkochhttps://github.com/pnpm/pnpm/pull/5253l/5253
fix: only set extraEnv for preferSymlinkedExecutables if it's not windows by @d3https://github.com/pnpm/pnpm/pull/5256l/5256

New Contributors

@timtong1982 made their first contributihttps://github.com/pnpm/pnpm/pull/5246l/5246

Full Changelog: pnpm/pnpm@v7.9.4...v7.9.5

`v7.9.4`

Compare Source

Patch Changes

Auto install peer dependencies when auto-install-peers is set to true and the lockfile is up to date #5213.
pnpm env: for Node.js<16 install the x64 build on Darwin ARM as ARM build is not available #5239.
pnpm env: log a message when the node.js tarball starts the download #5241.
Fix pnpm install --merge-git-branch-lockfile when the lockfile is up to date #5212.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

feat(cafs): extend cafs with getFilePathByModeInCafs by @d3https://github.com/pnpm/pnpm/pull/5232l/5232
fix: mergeGitBranchLockfiles when merged lockfile is up-to-date by @chengcybhttps://github.com/pnpm/pnpm/pull/5233l/5233
test: all test packages should be from the @pnpm.e2e scope by @&#8203https://github.com/pnpm/pnpm/pull/5211pm/pull/5211
fix: node<16 download fail on arm chips on macos by @ambar-arkhttps://github.com/pnpm/pnpm/pull/5239l/5239
feat(env): show state on fetching node by @JacobLinCohttps://github.com/pnpm/pnpm/pull/5241l/5241
Fix: install peerDeps which is not optional on headless install by @Shinyaigehttps://github.com/pnpm/pnpm/pull/5243l/5243

New Contributors

@ambar-arkin made their first contributihttps://github.com/pnpm/pnpm/pull/5239l/5239
@JacobLinCool made their first contributihttps://github.com/pnpm/pnpm/pull/5241l/5241
@Shinyaigeek made their first contributihttps://github.com/pnpm/pnpm/pull/5243l/5243

Full Changelog: pnpm/pnpm@v7.9.3...v7.9.4

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

renovate bot force-pushed the renovate/pnpm-7.x branch from bb0dd68 to b5aee86 Compare August 24, 2022 16:12

renovate bot changed the title ~~chore(deps): update pnpm to v7.9.4~~ chore(deps): update pnpm to v7.9.5 Aug 24, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from b5aee86 to 9a304d7 Compare September 4, 2022 10:33

renovate bot changed the title ~~chore(deps): update pnpm to v7.9.5~~ chore(deps): update pnpm to v7.10.0 Sep 4, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from 9a304d7 to 452a6ab Compare September 5, 2022 14:31

renovate bot changed the title ~~chore(deps): update pnpm to v7.10.0~~ chore(deps): update pnpm to v7.11.0 Sep 5, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from 452a6ab to 64c662c Compare September 7, 2022 08:46

renovate bot force-pushed the renovate/pnpm-7.x branch from 64c662c to 1ad856a Compare September 18, 2022 20:18

renovate bot changed the title ~~chore(deps): update pnpm to v7.11.0~~ chore(deps): update pnpm to v7.12.0 Sep 18, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from 1ad856a to 6e4f316 Compare September 20, 2022 01:37

renovate bot changed the title ~~chore(deps): update pnpm to v7.12.0~~ chore(deps): update pnpm to v7.12.1 Sep 20, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from 6e4f316 to 1e463d4 Compare September 22, 2022 20:31

renovate bot changed the title ~~chore(deps): update pnpm to v7.12.1~~ chore(deps): update pnpm to v7.11.0 Sep 22, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from 1e463d4 to b481914 Compare September 22, 2022 23:46

renovate bot changed the title ~~chore(deps): update pnpm to v7.11.0~~ chore(deps): update pnpm to v7.12.2 Sep 22, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from b481914 to c867fcd Compare October 3, 2022 02:27

renovate bot changed the title ~~chore(deps): update pnpm to v7.12.2~~ chore(deps): update pnpm to v7.13.0 Oct 3, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from c867fcd to 7148228 Compare October 4, 2022 11:16

renovate bot changed the title ~~chore(deps): update pnpm to v7.13.0~~ chore(deps): update pnpm to v7.13.1 Oct 4, 2022

renovate bot force-pushed the renovate/pnpm-7.x branch from 7148228 to 49a1367 Compare October 5, 2022 23:16

renovate bot changed the title ~~chore(deps): update pnpm to v7.13.1~~ chore(deps): update pnpm to v7.13.2 Oct 5, 2022

Update pnpm to v7.13.2

00cc674

renovate bot force-pushed the renovate/pnpm-7.x branch from 49a1367 to 00cc674 Compare October 9, 2022 00:11

renovate bot changed the title ~~chore(deps): update pnpm to v7.13.2~~ Update pnpm to v7.13.2 Oct 9, 2022

jade-gjz merged commit 60d8bdd into main Oct 9, 2022

renovate bot deleted the renovate/pnpm-7.x branch October 9, 2022 00:13

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update pnpm to v7.13.2 #21

Update pnpm to v7.13.2 #21

renovate bot commented Aug 23, 2022 •

edited

Update pnpm to v7.13.2 #21

Update pnpm to v7.13.2 #21

Conversation

renovate bot commented Aug 23, 2022 • edited

Release Notes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Minor Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Minor Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Minor Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Minor Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Configuration

renovate bot commented Aug 23, 2022 •

edited