Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 5, 2024

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

v9.11.0

Compare Source

v9.10.0: pnpm 9.10

Compare Source

Minor Changes

  • Support for a new CLI flag, --exclude-peers, added to the list and why commands. When --exclude-peers is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #​8506.

  • Added a new setting to package.json at pnpm.auditConfig.ignoreGhsas for ignoring vulnerabilities by their GHSA code #​6838.

    For instance:

    {
      "pnpm": {
        "auditConfig": {
          "ignoreGhsas": [
            "GHSA-42xw-2xvc-qx8m",
            "GHSA-4w2v-q235-vp99",
            "GHSA-cph5-m8f7-6c5x",
            "GHSA-vh95-rmgr-6w4m"
          ]
        }
      }
    }

Patch Changes

  • Throw an exception if pnpm switches to the same version of itself.
  • Reduce memory usage during peer dependencies resolution.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.9.0

Compare Source

v9.8.0

Compare Source

v9.7.1

Compare Source

v9.7.0: pnpm 9.7

Compare Source

Minor Changes

  • Added pnpm version management. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #​8363. This is the same field used by Corepack. Example:

    {
      "packageManager": "pnpm@9.3.0"
    }
  • Added the ability to apply patch to all versions #​8337.

    If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

  • Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[@​version] to allow the code editor to open the edit dir in the same file tree as the main project #​8379.

  • Substitute environment variables in config keys #​6679.

Patch Changes

  • pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project doesn't have an install script #​8293.
  • Print warnings to stderr #​8342.
  • Peer dependencies of optional peer dependencies should be automatically installed #​8323.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.6.0: pnpm 9.6

Compare Source

Minor Changes

  • Support specifying node version (via pnpm.executionEnv.nodeVersion in package.json) for running lifecycle scripts per each package in a workspace #​6720.
  • Overrides now support the catalogs: protocol #​8303.

Patch Changes

  • The pnpm deploy command now supports the catalog: protocol #​8298.
  • The pnpm outdated command now supports the catalog: protocol #​8304.
  • Correct the error message when trying to run pnpm patch without node_modules/.modules.yaml #​8257.
  • Silent reporting fixed with the pnpm exec command #​7608.
  • Add registries information to the calculation of dlx cache hash #​8299.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.5.0

Compare Source

v9.4.0

Compare Source

v9.3.0

Compare Source

Minor Changes

  • Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the peers-suffix-max-length setting #​8177.

Patch Changes

  • Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter-hide-prefix=false #​8174.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.2.0

Compare Source

Minor Changes

  • If package-manager-strict-version is set to true, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of package.json.

Patch Changes

  • Update @yarnpkg/pnp to the latest version, fixing issue with node: imports #​8161.
  • Deduplicate bin names to prevent race condition and corrupted bin scripts #​7833.
  • pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of package.json #​8087.
  • exec now also streams prefixed output when --recursive or --parallel is specified just as run does #​8065.

Platinum Sponsors

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from dd31f40 to 6188ae8 Compare June 10, 2024 15:50
@renovate renovate bot changed the title chore(deps): update pnpm to v9.2.0 chore(deps): update pnpm to v9.3.0 Jun 10, 2024
@renovate renovate bot changed the title chore(deps): update pnpm to v9.3.0 chore(deps): update pnpm to v9.4.0 Jun 17, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 6188ae8 to 181b027 Compare June 17, 2024 16:41
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 181b027 to fbbd9a7 Compare July 7, 2024 18:09
@renovate renovate bot changed the title chore(deps): update pnpm to v9.4.0 chore(deps): update pnpm to v9.5.0 Jul 7, 2024
@renovate renovate bot changed the title chore(deps): update pnpm to v9.5.0 chore(deps): update pnpm to v9.6.0 Jul 22, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from fbbd9a7 to f8037e5 Compare July 22, 2024 01:25
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from f8037e5 to 03a79a8 Compare August 7, 2024 01:43
@renovate renovate bot changed the title chore(deps): update pnpm to v9.6.0 chore(deps): update pnpm to v9.7.0 Aug 7, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 03a79a8 to d3cd98a Compare August 14, 2024 17:00
@renovate renovate bot changed the title chore(deps): update pnpm to v9.7.0 chore(deps): update pnpm to v9.7.1 Aug 14, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from d3cd98a to 24a784a Compare August 22, 2024 11:34
@renovate renovate bot changed the title chore(deps): update pnpm to v9.7.1 chore(deps): update pnpm to v9.8.0 Aug 22, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 24a784a to 46118f2 Compare August 26, 2024 16:27
@renovate renovate bot changed the title chore(deps): update pnpm to v9.8.0 chore(deps): update pnpm to v9.9.0 Aug 26, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 46118f2 to 77838ca Compare September 9, 2024 17:27
@renovate renovate bot changed the title chore(deps): update pnpm to v9.9.0 chore(deps): update pnpm to v9.10.0 Sep 9, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 77838ca to 8abb4ae Compare September 20, 2024 10:56
@renovate renovate bot changed the title chore(deps): update pnpm to v9.10.0 chore(deps): update pnpm to v9.11.0 Sep 20, 2024
@driimus driimus merged commit 2dfc68c into main Sep 26, 2024
4 checks passed
@driimus driimus deleted the renovate/pnpm-9.x branch September 26, 2024 21:43
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.

2 participants