Skip to content
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.

Update pnpm to v7.13.1 #5

Merged
merged 1 commit into from
Oct 26, 2022
Merged

Update pnpm to v7.13.1 #5

merged 1 commit into from
Oct 26, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 12, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm

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 !@​babel/*

    And it may be combined with other patterns:

      pnpm update @​babel/* !@​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
New Contributors

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

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

v7.8.0

Compare Source

Minor Changes

  • When publishConfig.directory is set, only symlink it to other workspace projects if publishConfig.linkDirectory is set to true. Otherwise, only use it for publishing #​5115.

Patch Changes

  • Don't incorrectly identify a lockfile out-of-date when the package has a publishConfig.directory field #​5124.
  • Don't crash when a config file contains a setting with an env variable that doesn't exist #​5093.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.7.1...v7.8.0

v7.7.1

Compare Source

Patch Changes

  • pnpm should not consider a lockfile out-of-date if auto-install-peers is set to true and the peer dependency is in devDependencies or optionalDependencies #​5080.
  • Don't incorrectly consider a lockfile out-of-date when workspace:^ or workspace:~ version specs are used in a workspace.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Full Changelog: pnpm/pnpm@v7.7.0...v7.7.1

v7.7.0

Compare Source

Minor Changes

  • Add experimental lockfile format that should merge conflict less in the importers section. Enabled by setting the use-inline-specifiers-lockfile-format = true feature flag in .npmrc.

    If this feature flag is committed to a repo, we recommend setting the minimum allowed version of pnpm to this release in the package.json engines field. Once this is set, older pnpm versions will throw on invalid lockfile versions.

  • Add publishDirectory field to the lockfile and relink the project when it changes.

  • verify-store-integrity=false makes pnpm skip checking the integrities of files in the global content-addressable store.

  • Allow to set only-built-dependencies[] through .npmrc.

Patch Changes

  • It should be possible to publish a package with local dependencies from a custom publish directory (set via publishConfig.directory) #​3901.
  • pnpm deploy should inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #​5078.
  • When a project in a workspace has a publishConfig.directory set, dependent projects should install the project from that directory #​3901
  • pnpm deploy: accept absolute paths and use cwd instead of workspaceDir for deploy target directory #​4980.
  • pnpm setup should update .zshrc in the right directory when a $ZDOTDIR is set.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

New Contributors

Full Changelog: pnpm/pnpm@v7.6.0...v7.7.0

v7.6.0

Compare Source

Minor Changes

  • A new setting supported: prefer-symlinked-executables. When true, pnpm will create symlinks to executables in
    node_modules/.bin instead of command shims (but on POSIX systems only).

    This setting is true by default when node-linker is set to hoisted.

    Related issue: #​4782.

  • When lockfile-include-tarball-url is set to true, every entry in pnpm-lock.yaml will contain the full URL to the package's tarball #​5054.

Patch Changes

  • pnpm deploy should include all dependencies by default #​5035.
  • Don't print warnings about file verifications. Just print info messages instead.
  • pnpm publish --help should print the --recursive and --filter options #​5019.
  • It should be possible to run exec/run/dlx with the --use-node-version option.
  • `pnpm

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 renovate bot added the renovate label May 12, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.0 Update pnpm to v7.1.1 May 17, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.1 Update pnpm to v7.1.0 May 18, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.0 Update pnpm to v7.1.2 May 19, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.2 Update pnpm to v7.1.3 May 22, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.3 Update pnpm to v7.1.5 May 24, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.5 Update pnpm to v7.1.6 May 27, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.6 Update pnpm to v7.1.7 May 29, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.7 Update pnpm to v7.1.8 Jun 5, 2022
@renovate renovate bot changed the title Update pnpm to v7.1.8 Update pnpm to v7.1.9 Jun 6, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from c35c8c5 to 24ff990 Compare June 10, 2022 16:15
@renovate renovate bot changed the title Update pnpm to v7.1.9 Update pnpm to v7.2.0 Jun 10, 2022
@renovate renovate bot changed the title Update pnpm to v7.2.0 Update pnpm to v7.2.1 Jun 11, 2022
@renovate renovate bot changed the title Update pnpm to v7.2.1 Update pnpm to v7.3.0 Jun 19, 2022
@renovate renovate bot changed the title Update pnpm to v7.3.0 Update pnpm to v7.4.0 Jun 28, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from 45c6e1c to 598b305 Compare June 30, 2022 13:15
@renovate renovate bot changed the title Update pnpm to v7.12.0 Update pnpm to v7.12.1 Sep 20, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from 7cea0d7 to 7811211 Compare September 22, 2022 20:14
@renovate renovate bot changed the title Update pnpm to v7.12.1 Update pnpm to v7.11.0 Sep 22, 2022
@renovate renovate bot changed the title Update pnpm to v7.11.0 Update pnpm to v7.12.2 Sep 23, 2022
@renovate renovate bot changed the title Update pnpm to v7.12.2 Update pnpm to v7.13.0 Oct 3, 2022
@renovate renovate bot changed the title Update pnpm to v7.13.0 Update pnpm to v7.13.1 Oct 4, 2022
@renovate renovate bot changed the title Update pnpm to v7.13.1 Update pnpm to v7.13.2 Oct 5, 2022
@renovate renovate bot changed the title Update pnpm to v7.13.2 Update pnpm to v7.13.3 Oct 9, 2022
@renovate renovate bot changed the title Update pnpm to v7.13.3 Update pnpm to v7.13.4 Oct 10, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from 998482e to 370e517 Compare October 16, 2022 20:07
@renovate renovate bot changed the title Update pnpm to v7.13.4 Update pnpm to v7.13.5 Oct 16, 2022
@renovate renovate bot changed the title Update pnpm to v7.13.5 Update pnpm to v7.13.6 Oct 20, 2022
@renovate renovate bot changed the title Update pnpm to v7.13.6 Update pnpm to v7.14.0 Oct 22, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from 2d4a5f6 to 3b1b958 Compare October 26, 2022 13:03
@renovate renovate bot changed the title Update pnpm to v7.14.0 Update pnpm to v7.13.1 Oct 26, 2022
@renovate renovate bot merged commit 560b2d8 into main Oct 26, 2022
@renovate renovate bot deleted the renovate/pnpm-7.x branch October 26, 2022 20:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants