chore(deps): update pnpm to v9 - autoclosed #47
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Warning Rate limit exceeded@renovate[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 28 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThe update involves changing the version of the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
1b04be6
to
2b1f2e8
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
2b1f2e8
to
9853129
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
0d0142d
to
775aa2d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
42b5c39
to
10f3187
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
10f3187
to
08d1a9e
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
08d1a9e
to
bdc72de
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
bdc72de
to
cc46f84
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
cc46f84
to
3e48d07
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Additional comments not posted (1)
package.json (1)
5-5: Verify compatibility with[email protected].The
pnpmversion has been updated from8.14.1to9.7.0. Ensure that this version is compatible with your project's dependencies and build processes.Verification successful
No breaking changes found in
[email protected]release notes.The update to
[email protected]introduces several minor improvements and patch changes without any listed breaking changes. It should be compatible with your project, but consider manually testing your build and dependency processes to ensure everything functions as expected.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility of pnpm version update with project dependencies. # Test: Check for any breaking changes or compatibility issues in pnpm 9.7.0 release notes. # Fetch the release notes from pnpm's GitHub repository. gh release view v9.7.0 --repo pnpm/pnpm --json body -q .bodyLength of output: 9177
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
3e48d07
to
d22beef
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis 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
from
d22beef
to
0707512
Compare
renovate
bot
changed the title
This PR contains the following updates:
8.14.1->9.8.0Release Notes
pnpm/pnpm (pnpm)
v9.8.0Compare Source
v9.7.1Compare Source
v9.7.0: pnpm 9.7Compare Source
Minor Changes
Added pnpm version management. If the
manage-package-manager-versionssetting is set totrue, pnpm will switch to the version specified in thepackageManagerfield ofpackage.json#8363. This is the same field used by Corepack. Example:{ "packageManager": "[email protected]" }Added the ability to apply patch to all versions #8337.
If the key of
pnpm.patchedDependenciesis 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 ofpkginstalled,pnpm patch pkgand subsequentpnpm patch-commit $edit_dirwill create an entry namedpkginpnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions ofpkgin the future.Change the default edit dir location when running
pnpm patchfrom a temporary directory tonode_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 installshould runnode-gyp rebuildif the project has abinding.gypfile even if the project doesn't have an install script #8293.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.6.0: pnpm 9.6Compare Source
Minor Changes
pnpm.executionEnv.nodeVersioninpackage.json) for running lifecycle scripts per each package in a workspace #6720.catalogs:protocol #8303.Patch Changes
pnpm deploycommand now supports thecatalog:protocol #8298.pnpm outdatedcommand now supports thecatalog:protocol #8304.pnpm patchwithoutnode_modules/.modules.yaml#8257.pnpm execcommand #7608.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.5.0Compare Source
v9.4.0Compare Source
v9.3.0Compare Source
Minor Changes
peers-suffix-max-lengthsetting #8177.Patch Changes
reporter-hide-prefixtotrueby default forpnpm exec. In order to show prefix, the user now has to explicitly setreporter-hide-prefix=false#8174.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.2.0Compare Source
Minor Changes
package-manager-strict-versionis set totrue, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field ofpackage.json.Patch Changes
@yarnpkg/pnpto the latest version, fixing issue withnode:imports #8161.package.json#8087.execnow also streams prefixed output when--recursiveor--parallelis specified just asrundoes #8065.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.1.4Compare Source
v9.1.3Compare Source
v9.1.2Compare Source
Patch Changes
pnpm licensesoutput are not misplaced anymore #8071.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.1.1Compare Source
v9.1.0Compare Source
v9.0.6Compare Source
v9.0.5Compare Source
v9.0.4Compare Source
v9.0.3Compare Source
v9.0.2Compare Source
v9.0.1Compare Source
v9.0.0Compare Source
Major Changes
Node.js v16 support discontinued
If you still require Node.js 16, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the
@pnpm/exepackage.Configuration updates:
dedupe-injected-deps: enabled by default.link-workspace-packages: disabled by default. This means that by default, dependencies will be linked from workspace packages only when they are specified using the workspace protocol.hoist-workspace-packages: enabled by default.enable-pre-post-scripts: enabled by default.~/.local/state/pnpm).package.jsonfile for apackageManagerfield. If this field is present and specifies a different package manager or a different version of pnpm than the one you're currently using, pnpm will not proceed. This ensures that you're always using the correct package manager and version that the project requires.Lockfile changes:
Dependency resolution changes:
Related issue: #7444.
Related PR: #7606.
pnpm licenses listprints license information of all versions of the same package in case different versions use different licenses. The format of thepnpm licenses list --jsonoutput has been changed #7528.A new command added for printing completion code to the console:
pnpm completion [shell]. The old command that modified the user's shell dotfiles has been removed #3083.When installing git-hosted dependencies, only pick the files that would be packed with the package #7638.
Minor Changes
It is now possible to install only a subdirectory from a Git repository.
For example,
pnpm add github:user/repo#path:packages/foowill add a dependency from thepackages/foosubdirectory.This new parameter may be combined with other supported parameters separated by
&. For instance, the next command will install the same package from thedevbranch:pnpm add github:user/repo#dev&path:packages/bar.Related issue: #4765.
Related PR: #7487.
node-gypupdated to version 10.PowerShell completion support added #7597.
Support
node-optionsoption inside.npmrcfile when running scripts #7596.Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported:
<registryURL>:certfile,<registryURL>:keyfile, and<registryURL>:ca. For instance:Related issue: #7427.
Related PR: #7626.
Add a field named
ignoredOptionalDependencies. This is an array of strings. If an optional dependency has its name included in this array, it will be skipped #7714.The checksum of the
.pnpmfile.cjsis saved into the lockfile. If the pnpmfile gets modified, the lockfile is reanalyzed to apply the changes #7662.Added cache for
pnpm dlx#5277.Patch Changes
--lockfile-onlyinstallation #1328.pnpm dlxshould not read settings from the current working directory #7916.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v8.15.9: pnpm 8.15.9Compare Source
Patch Changes
Platinum Sponsors
Gold Sponsors
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.
This PR was generated by Mend Renovate. View the repository job log.