Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

bump(deps): update pnpm to >=7.14.1 - autoclosed #2

Closed
wants to merge 1 commit into from
Closed

bump(deps): update pnpm to >=7.14.1 - autoclosed #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 30, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) >=7.9.0 -> >=7.14.1 age adoption passing confidence

Release Notes

pnpm/pnpm

v7.14.1

Compare Source

Patch Changes

  • pnpm list --long --json should print licenses and authors of packages #​5533.
  • Don't crash on lockfile with no packages field #​5553.
  • Version overrider should have higher priority then custom read package hook from .pnpmfile.cjs.
  • Don't print context information when running install for the pnpm dlx command.
  • Print a warning if a package.json has a workspaces field but there is no pnpm-workspace.yaml file #​5363.
  • It should be possible to set a custom home directory for pnpm by changing the PNPM_HOME environment variable.

Our Gold Sponsors

Our Silver Sponsors

v7.14.0

Compare Source

Minor Changes

  • Add pnpm doctor command to do checks for known common issues

Patch Changes

  • Ignore the always-auth setting.

    pnpm will never reuse the registry auth token for requesting the package tarball, if the package tarball is hosted on a different domain.

    So, for example, if your registry is at https://company.registry.com/ but the tarballs are hosted at https://tarballs.com/, then you will have to configure the auth token for both domains in your .npmrc:

    @​my-company:registry=https://company.registry.com/
//company.registry.com/=SOME_AUTH_TOKEN
//tarballs.com/=SOME_AUTH_TOKEN

Our Gold Sponsors

Our Silver Sponsors

v7.13.6

Compare Source

Patch Changes
  • Downgrade @pnpm/npm-conf to remove annoying builtin warning #​5518.
  • pnpm link --global <pkg> should not change the type of the dependency #​5478.
  • When the pnpm outdated command fails, print in which directory it failed.
Our Gold Sponsors
Our Silver Sponsors

v7.13.5

Compare Source

Patch Changes

  • Print a warning when cannot read the built-in npm configuration.
  • Also include missing deeply linked workspace packages at headless installation #​5034.
  • pnpm outdated should work when the package tarballs are hosted on a domain that differs from the registry's domain #​5492.
  • strict-peer-dependencies is set to false by default.

Our Gold Sponsors

Our Silver Sponsors

v7.13.4

Compare Source

Patch Changes

  • pnpm link <pkg> --global should work when a custom target directory is specified with the --dir CLI option #​5473.
  • It should be possible to override dependencies with local packages using overrides #​5443.

Our Gold Sponsors

Our Silver Sponsors

v7.13.3

Compare Source

Patch Changes

  • Don't crash when auto-install-peers is set to true and installation is done on a workspace with that has the same dependencies in multiple projects #​5454.
  • Add global option in pnpm link --help #​5461.
  • Show execution time on install, update, add, and remove #​1021.
  • Fix the return path of pnpm pack, when a custom destination directory is used #​5471.

Our Gold Sponsors

Our Silver Sponsors

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

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": {
      "[email protected]": "patches/[email protected]"
    },
    "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 [email protected] --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

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, check this box

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 0125628 to 711e557 Compare September 4, 2022 11:31
@renovate renovate bot changed the title Update pnpm to >=7.9.5 Update pnpm to >=7.10.0 Sep 4, 2022
@codecov-commenter
Copy link

codecov-commenter commented Sep 4, 2022 •
edited by codecov bot
Loading

Codecov Report

Merging #2 (62e7702) into main (764757c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #2   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            2         2           
=========================================
  Hits             2         2

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@netlify
Copy link

netlify bot commented Sep 4, 2022 •
edited
Loading

✅ Deploy Preview for sticky-birthday ready!

Name Link
🔨 Latest commit 9b9b4d4
🔍 Latest deploy log https://app.netlify.com/sites/sticky-birthday/deploys/634c63c0db273c000a64a7ef
😎 Deploy Preview https://deploy-preview-2--sticky-birthday.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@renovate renovate bot changed the title Update pnpm to >=7.10.0 Update pnpm to >=7.11.0 Sep 5, 2022
@renovate renovate bot changed the title Update pnpm to >=7.11.0 Update pnpm to >=7.12.0 Sep 18, 2022
@renovate renovate bot changed the title Update pnpm to >=7.12.0 Update pnpm to >=7.12.1 Sep 20, 2022
@renovate renovate bot changed the title Update pnpm to >=7.12.1 Update pnpm to >=7.11.0 Sep 22, 2022
@renovate renovate bot changed the title Update pnpm to >=7.11.0 Update pnpm to >=7.12.2 Sep 22, 2022
@renovate renovate bot changed the title Update pnpm to >=7.12.2 bump(deps): update pnpm to >=7.12.2 Sep 27, 2022
@birthdayresearch-bot birthdayresearch-bot added the kind/dependencies Pull requests that update a dependency file label Sep 27, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.12.2 bump(deps): update pnpm to >=7.13.0 Oct 3, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.13.0 bump(deps): update pnpm to >=7.13.1 Oct 4, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.13.1 bump(deps): update pnpm to >=7.13.2 Oct 5, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.13.2 bump(deps): update pnpm to >=7.13.3 Oct 9, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.13.3 bump(deps): update pnpm to >=7.13.4 Oct 10, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.13.4 bump(deps): update pnpm to >=7.13.5 Oct 16, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.13.5 bump(deps): update pnpm to >=7.13.6 Oct 20, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.13.6 bump(deps): update pnpm to >=7.14.0 Oct 22, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.14.0 bump(deps): update pnpm to >=7.14.1 Oct 29, 2022
@renovate renovate bot changed the title bump(deps): update pnpm to >=7.14.1 bump(deps): update pnpm to >=7.14.1 - autoclosed Oct 31, 2022
@renovate renovate bot closed this Oct 31, 2022
@renovate renovate bot deleted the renovate/pnpm-7.x branch October 31, 2022 05:28
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
kind/dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@codecov-commenter @birthdayresearch-bot