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

chore(deps): update pnpm to v9.15.1 #996

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2024

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

v9.15.1

Compare Source

v9.15.0

Compare Source

v9.14.4

Compare Source

v9.14.3

Compare Source

v9.14.2

Compare Source

Patch Changes

  • pnpm publish --json should work #​8788.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me

v9.14.1

Compare Source

Minor Changes

  • Added support for pnpm pack --json to print packed tarball and contents in JSON format #​8765.

Patch Changes

  • pnpm exec should print a meaningful error message when no command is provided #​8752.
  • pnpm setup should remove the CLI from the target location before moving the new binary #​8173.
  • Fix ERR_PNPM_TARBALL_EXTRACT error while installing a dependency from GitHub having a slash in branch name #​7697.
  • Don't crash if the use-node-version setting is used and the system has no Node.js installed #​8769.
  • Convert settings in local .npmrc files to their correct types. For instance, child-concurrency should be a number, not a string #​5075.
  • pnpm should fail if a project requires a different package manager even if manage-package-manager-versions is set to true.
  • pnpm init should respect the --dir option #​8768.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me

v9.14.0

Compare Source

v9.13.2: pnpm 9.13.2

Compare Source

Patch Changes

  • Detection of circular peer dependencies should not crash with aliased dependencies #​8759. Fixes a regression introduced in the previous version.
  • Fix race condition of symlink creations caused by multiple parallel dlx processes.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me

Silver Sponsors

Leniolabs_ Vercel
Depot moonrepo
devowl.io Cerbos
vlt Vite

v9.13.1: pnpm 9.13.1

Compare Source

Patch Changes

  • Fixed some edge cases where resolving circular peer dependencies caused a dead lock #​8720.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me

Silver Sponsors

Leniolabs_ Vercel
Depot moonrepo
devowl.io Cerbos
vlt Vite

v9.13.0: pnpm 9.13

Compare Source

Minor Changes

  • The self-update now accepts a version specifier to install a specific version of pnpm. E.g.:

    pnpm self-update 9.5.0
    

    or

    pnpm self-update next-10
    

Patch Changes

  • Fix Cannot read properties of undefined (reading 'name') that is printed while trying to render the missing peer dependencies warning message #​8538.

Platinum Sponsors

Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me

Silver Sponsors

Leniolabs_ Vercel
Depot moonrepo
devowl.io Cerbos
vlt Vite

v9.12.3

Compare Source

Patch Changes
  • Don't purge node_modules, when typing "n" in the prompt that asks whether to remove node_modules before installation #​8655.
  • Fix a bug causing pnpm to infinitely spawn itself when manage-package-manager-versions=true is set and the .tools directory is corrupt.
  • Use crypto.hash, when available, for improved performance #​8629.
  • Fixed a race condition in temporary file creation in the store by including worker thread ID in filename. Previously, multiple worker threads could attempt to use the same temporary file. Temporary files now include both process ID and thread ID for uniqueness #​8703.
  • All commands should read settings from the package.json at the root of the workspace #​8667.
  • When manage-package-manager-versions is set to true, errors spawning a self-managed version of pnpm will now be shown (instead of being silent).
  • Pass the find command to npm, it is an alias for npm search

v9.12.2

Compare Source

Patch Changes
  • When checking whether a file in the store has executable permissions, the new approach checks if at least one of the executable bits (owner, group, and others) is set to 1. Previously, a file was incorrectly considered executable only when all the executable bits were set to 1. This fix ensures that files with any executable permission, regardless of the user class, are now correctly identified as executable #​8546.

v9.12.1

Compare Source

Patch Changes
  • pnpm update --latest should not update the automatically installed peer dependencies #​6657.
  • pnpm publish should be able to publish from a local tarball #​7950.
  • The pnpx command should work correctly on Windows, when pnpm is installed via the standalone installation script #​8608.
  • Prevent EBUSY errors caused by creating symlinks in parallel dlx processes #​8604.
  • Fix maximum call stack size exceeded error related to circular workspace dependencies #​8599.

v9.12.0

Compare Source

Minor Changes
  • Fix peer dependency resolution dead lock #​8570. This change might change some of the keys in the snapshots field inside pnpm-lock.yaml but it should happen very rarely.

  • pnpm outdated command supports now a --sort-by=name option for sorting outdated dependencies by package name #​8523.

  • Added the ability for overrides to remove dependencies by specifying "-" as the field value #​8572. For example, to remove lodash from the dependencies, use this configuration in package.json:

    {
      "pnpm": {
        "overrides": {
          "lodash": "-"
        }
      }
    }
Patch Changes
  • Fixed an issue where pnpm list --json pkg showed "private": false for a private package #​8519.
  • Packages with libc that differ from pnpm.supportedArchitectures.libc are not downloaded #​7362.
  • Prevent ENOENT errors caused by running store prune in parallel #​8586.
  • Add issues alias to pnpm bugs #​8596.

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 these updates 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 added dependencies Pull requests that update a dependency file renovatebot labels Oct 2, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from dce54b4 to 7069ebe Compare October 4, 2024 07:22
@renovate renovate bot changed the title chore(deps): update pnpm to v9.12.0 chore(deps): update pnpm to v9.12.1 Oct 7, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 7069ebe to 321bf96 Compare October 7, 2024 16:27
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 321bf96 to c20e64d Compare October 16, 2024 16:55
@renovate renovate bot changed the title chore(deps): update pnpm to v9.12.1 chore(deps): update pnpm to v9.12.2 Oct 16, 2024
@renovate renovate bot changed the title chore(deps): update pnpm to v9.12.2 chore(deps): update pnpm to v9.12.3 Oct 28, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 3b3cff2 to e662f31 Compare October 30, 2024 13:12
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from e662f31 to 68ec5f0 Compare November 13, 2024 13:55
@renovate renovate bot changed the title chore(deps): update pnpm to v9.12.3 chore(deps): update pnpm to v9.13.0 Nov 13, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 68ec5f0 to 4119059 Compare November 14, 2024 19:22
@renovate renovate bot changed the title chore(deps): update pnpm to v9.13.0 chore(deps): update pnpm to v9.13.1 Nov 14, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 4119059 to d2ab6bd Compare November 15, 2024 03:34
@renovate renovate bot changed the title chore(deps): update pnpm to v9.13.1 chore(deps): update pnpm to v9.13.2 Nov 15, 2024
@renovate renovate bot changed the title chore(deps): update pnpm to v9.13.2 chore(deps): update pnpm to v9.14.1 Nov 20, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 660a66d to f897155 Compare November 20, 2024 11:48
@renovate renovate bot changed the title chore(deps): update pnpm to v9.14.1 chore(deps): update pnpm to v9.14.2 Nov 20, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from f897155 to 0be0373 Compare November 28, 2024 17:15
@renovate renovate bot changed the title chore(deps): update pnpm to v9.14.2 chore(deps): update pnpm to v9.14.3 Nov 28, 2024
@renovate renovate bot changed the title chore(deps): update pnpm to v9.14.3 chore(deps): update pnpm to v9.14.4 Nov 29, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from ded0708 to 72a41f1 Compare December 4, 2024 07:09
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 72a41f1 to 1588886 Compare December 6, 2024 16:20
@renovate renovate bot changed the title chore(deps): update pnpm to v9.14.4 chore(deps): update pnpm to v9.15.0 Dec 6, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 1588886 to a837f2d Compare December 20, 2024 01:28
@renovate renovate bot changed the title chore(deps): update pnpm to v9.15.0 chore(deps): update pnpm to v9.15.1 Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file renovatebot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants