Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update pnpm to v7.12.2 #20

Merged
merged 1 commit into from Sep 23, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 6, 2022

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm

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

New Contributors

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

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

New Contributors

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

New Contributors

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

New Contributors

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
New Contributors

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

New Contributors

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

v7.9.3

Compare Source

Patch Changes

  • Remove legacy signal handlers #​5224

Our Gold Sponsors

Our Silver Sponsors

What's Changed

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

v7.9.2

Compare Source

Patch Changes

  • When the same package is both in "peerDependencies" and in "dependencies", treat this dependency as a peer dependency if it may be resolved from the dependencies of parent packages #​5210.
  • Update node-gyp to v9.
  • Update the compatibility database.

Our Gold Sponsors

Our Silver Sponsors

v7.9.1

Compare Source

Patch Changes

  • pnpm setup: don't use setx to set env variables on Windows.

Our Gold Sponsors

Our Silver Sponsors

v7.9.0

Compare Source

Minor Changes

  • When ignore-dep-scripts is true, ignore scripts of dependencies but run the scripts of the project.
  • When ignore-compatibility-db is set to true, the compatibility database will not be used to patch dependencies #​5132.
  • Print the versions of packages in peer dependency warnings and errors.
  • Support a new hook for passing a custom package importer to the store controller.

Patch Changes

  • Don't print the same deprecation warning multiple times.
  • On POSIX pnpm setup should suggest users to source the config instead of restarting the terminal.
  • Installing a package with bin that points to an .exe file on Windows #​5159.
  • Fix bug where the package manifest was not resolved if verify-store-integrity is set to false.
  • Fix sorting of keys in lockfile to make it more deterministic and prevent unnecessary churn in the lockfile #​5151.
  • Don't create a separate bundle for pnpx.

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

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

@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from 18dffac to 5fcd86b Compare August 17, 2022 10:22
@renovate renovate bot changed the title chore(deps): update pnpm to v7.9.0 chore(deps): update pnpm to v7.9.3 Aug 17, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 3 times, most recently from a3ff0da to 4bd5b99 Compare August 23, 2022 14:11
@renovate renovate bot changed the title chore(deps): update pnpm to v7.9.3 chore(deps): update pnpm to v7.9.4 Aug 23, 2022
@renovate 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 renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from 9c70992 to 97c1963 Compare September 4, 2022 11:52
@renovate 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 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 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 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 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 renovate bot changed the title chore(deps): update pnpm to v7.11.0 chore(deps): update pnpm to v7.12.2 Sep 23, 2022
@liuxingyu521 liuxingyu521 merged commit d169bc8 into main Sep 23, 2022
@renovate renovate bot deleted the renovate/pnpm-7.x branch September 23, 2022 01:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant