Skip to content
This repository was archived by the owner on Oct 1, 2023. It is now read-only.

chore(deps): update pnpm to v7.14.0#78

Merged
kodiakhq[bot] merged 1 commit intomainfrom
renovate/pnpm-7.x
Oct 22, 2022
Merged

chore(deps): update pnpm to v7.14.0#78
kodiakhq[bot] merged 1 commit intomainfrom
renovate/pnpm-7.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Oct 13, 2022

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm

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


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.

@vercel
Copy link
Copy Markdown

vercel bot commented Oct 13, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
sugar ✅ Ready (Inspect) Visit Preview Oct 22, 2022 at 4:12PM (UTC)

@renovate renovate bot force-pushed the renovate/pnpm-7.x branch from 8b6000c to c494b45 Compare October 16, 2022 21:16
@renovate renovate bot changed the title chore(deps): update pnpm to v7.13.4 chore(deps): update pnpm to v7.13.5 Oct 16, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch from c494b45 to 879c64b Compare October 20, 2022 11:55
@renovate renovate bot changed the title chore(deps): update pnpm to v7.13.5 chore(deps): update pnpm to v7.13.6 Oct 20, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch from 879c64b to c740ba8 Compare October 22, 2022 16:11
@renovate renovate bot changed the title chore(deps): update pnpm to v7.13.6 chore(deps): update pnpm to v7.14.0 Oct 22, 2022
@kodiakhq kodiakhq bot merged commit 5bc1dc8 into main Oct 22, 2022
@kodiakhq kodiakhq bot deleted the renovate/pnpm-7.x branch October 22, 2022 20:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant