chore(deps): update pnpm to v9 #12

renovate · 2024-05-01T01:32:04Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`8.9.0` -> `9.14.2`

Release Notes

pnpm/pnpm (pnpm)

`v9.14.2`

Compare Source

Patch Changes

pnpm publish --json should work #8788.

Platinum Sponsors

Gold Sponsors

`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

Gold Sponsors

`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

Gold Sponsors

Silver Sponsors

`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

Gold Sponsors

Silver Sponsors

`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

Gold Sponsors

Silver Sponsors

`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.

`v9.11.0`

Compare Source

Minor Changes

Experimental: added pnpm cache commands for inspecting the metadata cache #8512.

Patch Changes

Fix a regression in which pnpm deploy with node-linker=hoisted produces an empty node_modules directory #6682.
Don't print a warning when linking packages globally #4761.
pnpm deploy should work in workspace with shared-workspace-lockfile=false #8475.

`v9.10.0`

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.

`v9.9.0`

Compare Source

Minor Changes

Minor breaking change. This change might result in resolving your peer dependencies slightly differently but we don't expect it to introduce issues.

We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.

When a peer dependency is a prod dependency somewhere in the dependency graph (with the same version), pnpm will resolve the peers of that peer dependency in the same way across the subgraph.

For example, we have react-dom in the peer deps of the form and button packages. card has react-dom and react as regular dependencies and card is a dependency of form.

These are the direct dependencies of our example project:
```
form
react@16
react-dom@16
```
These are the dependencies of card:
```
button
react@17
react-dom@16
```
When resolving peers, pnpm will not re-resolve react-dom for card, even though card shadows react@16 from the root with react@17. So, all 3 packages (form, card, and button) will use react-dom@16, which in turn uses react@16. form will use react@16, while card and button will use react@17.

Before this optimization react-dom@16 was duplicated for the card, so that card and button would use a react-dom@16 instance that uses react@17.

Before the change:
```
form
-> react-dom@16(react@16)
-> react@16
card
-> react-dom@16(react@17)
-> react@17
button
-> react-dom@16(react@17)
-> react@17
```
After the change
```
form
-> react-dom@16(react@16)
-> react@16
card
-> react-dom@16(react@16)
-> react@17
button
-> react-dom@16(react@16)
-> react@17
```

Patch Changes

pnpm deploy should write the node_modules/.modules.yaml to the node_modules directory within the deploy directory #7731.
Don't override a symlink in node_modules if it already points to the right location pnpm/symlink-dir#54.

`v9.8.0`

Compare Source

Minor Changes

Added a new command for upgrading pnpm itself when it isn't managed by Corepack: pnpm self-update. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #8424.

When executed in a project that has a packageManager field in its package.json file, pnpm will update its version in the packageManager field.

Patch Changes

CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and use-node-version is set.
pnpm setup should never switch to another version of pnpm.

This fixes installation with the standalone script from a directory that has a package.json with the packageManager field. pnpm was installing the version of pnpm specified in the packageManager field due to this issue.
Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #8431.
Remember the state of edit dir, allow running pnpm patch-commit the second time without having to re-run pnpm patch.

`v9.7.1`

Compare Source

Patch Changes

Fixed passing public-hoist-pattern and hoist-pattern via env variables #8339.
pnpm setup no longer creates Batch/Powershell scripts on Linux and macOS #8418.
When dlx uses cache, use the real directory path not the symlink to the cache #8421.
pnpm exec now supports executionEnv #8356.
Remove warnings for non-root pnpm field, add warnings for non-root pnpm subfields that aren't executionEnv #8143.
Replace semver in "peerDependency" with workspace protocol #8355.
Fix a bug in patch-commit in which relative path is rejected #8405.
Update Node.js in @pnpm/exe to v20.

`v9.7.0`

Compare Source

Minor Changes

Added pnpm version management to pnpm. 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": "[email protected]"
}
```
Added the ability to apply patch to all versions:
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 it is a package name and an exact version (e.g. [email protected]), pnpm will attempt to apply the patch to that exact version only. Failures will
cause pnpm to fail.

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.

If there are multiple versions of pkg installed, pnpm patch pkg will ask which version to edit and whether to attempt to apply the patch to all.
If the user chooses to apply the patch to all, pnpm patch-commit $edit_dir would create a pkg entry in pnpm.patchedDependencies.
If the user chooses not to apply the patch to all, pnpm patch-commit $edit_dir would create a [email protected] entry in pnpm.patchedDependencies with
x.y.z being the version the user chose to edit.

If the user runs pnpm patch [email protected] with x.y.z being the exact version of pkg that has been installed, pnpm patch-commit $edit_dir will always
create a [email protected] entry in pnpm.patchedDependencies.
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.
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.

`v9.6.0`

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.

`v9.5.0`

Compare Source

Minor Changes

Added support for catalogs 8122.

Catalogs may be declared in the pnpm-workspace.yaml file. For example:

`v9.4.0`

Compare Source

Minor Changes

Some registries allow the exact same content to be published under different package names and/or versions. This breaks the validity checks of packages in the store. To avoid errors when verifying the names and versions of such packages in the store, you may now set the strict-store-pkg-content-check setting to false #4724.

Patch Changes

Fix package-manager-strict-version missing in config #8195.
If install is performed on a subset of workspace projects, always create an up-to-date lockfile first. So, a partial install can be performed only on a fully resolved (non-partial) lockfile #8165.
Handle workspace protocol with any semver range specifier, when used in peer dependencies #7578.

`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.

`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.

`v9.1.4`

Compare Source

Patch Changes

Improved the performance of the resolution stage by changing how missing peer dependencies are detected #8144.

`v9.1.3`

Compare Source

Patch Changes

Fix a bug in which a dependency that is both optional for one package but non-optional for another is omitted when optional=false #8066.
Clear resolution cache before starting peer dependencies resolution #8109.
Reduce memory usage by peer dependencies resolution #8072.

`v9.1.2`

Compare Source

Patch Changes

Reduced memory usage during peer dependencies resolution #8084.
Details in the pnpm licenses output are not misplaced anymore #8071.

`v9.1.1`

Compare Source

Patch Changes

Improve the performance of the peers resolution stage by utilizing more cache #8058.
Overrides with link: now preserve absolute path #8053.
Fix incorrect path when resolving relative file: overrides for workspace package #8053.
Print a better error message when resolution-mode is set to time-based and the registry fails to return the "time" field in the package's metadata.
Fix shell completion on MinGW-w64 environment.

`v9.1.0`

Compare Source

Minor Changes

New setting called virtual-store-dir-max-length added to modify the maximum allowed length of the directories inside node_modules/.pnpm. The default length is set to 120 characters. This setting is particularly useful on Windows, where there is a limit to the maximum length of a file path #7355.

Patch Changes

A dependency is hoisted to resolve an optional peer dependency only if it satisf

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - "before 4am on the first day of the month" (UTC).

🚦 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.

coderabbitai · 2024-05-01T01:32:09Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The updates involve changing the package manager version for the @uni-helper/localforage-adapter from [email protected] to [email protected] and then to [email protected]. These changes reflect an ongoing enhancement of package management tools while keeping other package metadata unchanged.

Changes

File	Change Summary
package.json	Updated `packageManager` from `[email protected]` to `[email protected]` and then to `[email protected]`

Poem

In the garden where the code does play,
A bunny hops with joy today! 🐇
With pnpm now at version nine,
All dependencies align just fine.
Hooray for updates, fresh and bright,
A leap toward packaging delight! 🌟

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7e263bf and acdca8f.

Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

package.json (1 hunks)

Files skipped from review due to trivial changes (1)

package.json

coderabbitai

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between acdca8f and 3f0d6e6.

Files ignored due to path filters (1)

pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

package.json (1 hunks)

Files skipped from review due to trivial changes (1)

package.json

renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 2a32ff0 to 3298634 Compare May 16, 2024 02:57

renovate bot force-pushed the renovate/pnpm-9.x branch from 3298634 to 75ece7c Compare May 23, 2024 22:21

pull-request-size bot added the size/XXL label May 23, 2024

renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from b700b10 to 6b2d260 Compare June 2, 2024 12:06

renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 00a1a7b to 6c1f415 Compare June 13, 2024 13:07

renovate bot force-pushed the renovate/pnpm-9.x branch from 6c1f415 to 5f254ba Compare June 20, 2024 16:42

renovate bot force-pushed the renovate/pnpm-9.x branch from 5f254ba to 2496ffc Compare July 10, 2024 17:26

renovate bot force-pushed the renovate/pnpm-9.x branch from 2496ffc to 84754bf Compare July 25, 2024 01:25

renovate bot force-pushed the renovate/pnpm-9.x branch from 84754bf to e05db3c Compare August 10, 2024 02:51

renovate bot force-pushed the renovate/pnpm-9.x branch from e05db3c to acdca8f Compare August 17, 2024 15:07

coderabbitai bot reviewed Aug 17, 2024

View reviewed changes

renovate bot force-pushed the renovate/pnpm-9.x branch from acdca8f to 3f0d6e6 Compare August 25, 2024 14:23

coderabbitai bot reviewed Aug 25, 2024

View reviewed changes

renovate bot force-pushed the renovate/pnpm-9.x branch from 3f0d6e6 to 902be58 Compare August 29, 2024 17:15

renovate bot force-pushed the renovate/pnpm-9.x branch from 902be58 to 57f4c6b Compare September 12, 2024 14:16

renovate bot force-pushed the renovate/pnpm-9.x branch from 57f4c6b to adad38f Compare September 23, 2024 12:45

renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from dc57aa7 to 1324e65 Compare October 10, 2024 17:01

renovate bot force-pushed the renovate/pnpm-9.x branch from 1324e65 to 1d1e6cb Compare October 19, 2024 15:49

renovate bot force-pushed the renovate/pnpm-9.x branch from 1d1e6cb to cfb6515 Compare October 31, 2024 05:18

renovate bot force-pushed the renovate/pnpm-9.x branch 4 times, most recently from 3df06ba to d896b14 Compare November 23, 2024 01:47

chore(deps): update pnpm to v9

83039e0

renovate bot force-pushed the renovate/pnpm-9.x branch from d896b14 to 83039e0 Compare November 23, 2024 12:34

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update pnpm to v9 #12

chore(deps): update pnpm to v9 #12

renovate bot commented May 1, 2024 •

edited

Loading

coderabbitai bot commented May 1, 2024 •

edited

Loading

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

coderabbitai bot left a comment

coderabbitai bot left a comment

chore(deps): update pnpm to v9 #12

Are you sure you want to change the base?

chore(deps): update pnpm to v9 #12

Conversation

renovate bot commented May 1, 2024 • edited Loading

Release Notes

Patch Changes

Platinum Sponsors

Gold Sponsors

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.13.2: pnpm 9.13.2

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v9.13.1: pnpm 9.13.1

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v9.13.0: pnpm 9.13

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

coderabbitai bot commented May 1, 2024 • edited Loading

Review skipped

Walkthrough

Changes

Poem

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

coderabbitai bot left a comment

Choose a reason for hiding this comment

coderabbitai bot left a comment

Choose a reason for hiding this comment

renovate bot commented May 1, 2024 •

edited

Loading

`v9.13.2`: pnpm 9.13.2

`v9.13.1`: pnpm 9.13.1

`v9.13.0`: pnpm 9.13

coderabbitai bot commented May 1, 2024 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)