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

Update pnpm to v7.18.0 #8

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update pnpm to v7.18.0 #8

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 24, 2022

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm

v7.18.0

Compare Source

Minor Changes

  • Overrides may be defined as a reference to a spec for a direct dependency by prefixing the name of the package you wish the version to match with a `# pnpm.

    {
      "dependencies": {
        "foo": "^1.0.0"
      },
      "overrides": {
        // the override is defined as a reference to the dependency
        "foo": "$foo",
        // the referenced package does not need to match the overridden one
        "bar": "$foo"
      }
    }

    Issue: #​5703

Patch Changes

  • pnpm audit should work when the project's package.json has no version field #​5728
  • Dependencies specified via * should be updated to semver ranges by pnpm update #​5681.
  • It should be possible to override a dependency with a local package using relative path from the workspace root directory #​5493.
  • Exit with non-zero exit code when child process exits with a non-zero exit clode #​5525.
  • pnpm add should prefer local projects from the workspace, even if they use prerelease versions #​5316

Our Gold Sponsors

Our Silver Sponsors

v7.17.1

Compare Source

Patch Changes

  • pnpm set-script and pnpm pkg are passed through to npm #​5683.
  • pnpm publish <tarball path> should exit with non-0 exit code when publish fails #​5396.
  • readPackage hooks should not modify the package.json files in a workspace #​5670.
  • Comments in package.json5 are preserver #​2008.
  • pnpm setup should create PNPM_HOME as a non-expandable env variable on Windows #​4658.
  • Fix the CLI help of the pnpm licenses command.

Our Gold Sponsors

Our Silver Sponsors

v7.17.0

Compare Source

Minor Changes

  • Added a new command pnpm licenses list, which displays the licenses of the packages #​2825

Patch Changes

  • pnpm update --latest !foo should not update anything if the only dependency in the project is the ignored one #​5643.
  • pnpm audit should send the versions of workspace projects for audit.
  • Hoisting with symlinks should not override external symlinks and directories in the root of node_modules.
  • The pnpm.updateConfig.ignoreDependencies setting should work with multiple dependencies in the array #​5639.

Our Gold Sponsors

Our Silver Sponsors

v7.16.1

Compare Source

Patch Changes

  • Sync all injected dependencies when hoisted node linker is used #​5630

Our Gold Sponsors

Our Silver Sponsors

v7.16.0

Compare Source

Minor Changes

  • Support pnpm env list to list global or remote Node.js versions #​5546.

Patch Changes

  • Replace environment variable placeholders with their values, when reading .npmrc files in subdirectories inside a workspace #​2570.
  • Fix an error that sometimes happen on projects with linked local dependencies #​5327.

Our Gold Sponsors

Our Silver Sponsors

v7.15.0

Compare Source

Minor Changes
  • Support --format=json option to output outdated packages in JSON format with outdated command #​2705.

    pnpm outdated --format=json
    #or
    pnpm outdated --json
  • A new setting supported for ignoring vulnerabilities by their CVEs. The ignored CVEs may be listed in the pnpm.auditConfig.ignoreCves field of package.json. For instance:

    {
      "pnpm": {
        "auditConfig": {
          "ignoreCves": [
            "CVE-2019-10742",
            "CVE-2020-28168",
            "CVE-2021-3749",
            "CVE-2020-7598"
          ]
        }
      }
    }
Patch Changes
  • The reporter should not crash when the CLI process is kill during lifecycle scripts execution #​5588.
  • Installation shouldn't fail when the injected dependency has broken symlinks. The broken symlinks should be just skipped #​5598.
Our Gold Sponsors
Our Silver Sponsors

v7.14.2

Compare Source

Patch Changes
  • Don't fail if cannot override the name field of the error object #​5572.
  • Don't fail on rename across devices.
Our Gold Sponsors
Our Silver Sponsors

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:

    @&#8203;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 [#​537

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 changed the title Update pnpm to v7.9.5 Update pnpm to v7.10.0 Sep 4, 2022
@renovate renovate bot changed the title Update pnpm to v7.10.0 Update pnpm to v7.11.0 Sep 5, 2022
@renovate renovate bot changed the title Update pnpm to v7.11.0 Update pnpm to v7.12.0 Sep 18, 2022
@renovate renovate bot changed the title Update pnpm to v7.12.0 Update pnpm to v7.12.1 Sep 20, 2022
@renovate renovate bot changed the title Update pnpm to v7.12.1 Update pnpm to v7.11.0 Sep 22, 2022
@renovate renovate bot force-pushed the renovate/pnpm-7.x branch 2 times, most recently from b004130 to 165973c Compare September 23, 2022 00:29
@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 force-pushed the renovate/pnpm-7.x branch 2 times, most recently from c6d3732 to 61d0649 Compare October 5, 2022 22:11
@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 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 changed the title Update pnpm to v7.14.0 Update pnpm to v7.14.1 Oct 29, 2022
@renovate renovate bot changed the title Update pnpm to v7.14.1 Update pnpm to v7.14.2 Nov 2, 2022
@renovate renovate bot changed the title Update pnpm to v7.14.2 Update pnpm to v7.15.0 Nov 10, 2022
@renovate renovate bot changed the title Update pnpm to v7.15.0 Update pnpm to v7.16.0 Nov 14, 2022
@renovate renovate bot changed the title Update pnpm to v7.16.0 Update pnpm to v7.16.1 Nov 16, 2022
@renovate renovate bot changed the title Update pnpm to v7.16.1 Update pnpm to v7.17.0 Nov 20, 2022
@renovate renovate bot changed the title Update pnpm to v7.17.0 Update pnpm to v7.17.1 Nov 27, 2022
@renovate renovate bot changed the title Update pnpm to v7.17.1 Update pnpm to v7.18.0 Dec 4, 2022
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

0 participants