chore(deps): update pnpm to v9.15.9 #16
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.15.0+sha512.76e2379760a4328ec4415815bcd6628dee727af3779aaa4c914e3944156c4299921a89f976381ee107d41f12cfa4b66681ca9c718f0668fa0831ed4c6d8ba56c->9.15.9Release Notes
pnpm/pnpm (pnpm)
v9.15.9: pnpm 9.15.9Compare Source
Patch Changes
Platinum Sponsors
Gold Sponsors
v9.15.8: pnpm 9.15.8Compare Source
Patch Changes
pnpm self-updateshould always update the version in thepackageManagerfield ofpackage.json.--silentreporting is used.--loglevelis set toerror, don't show installation summary, execution time, and big tarball download progress.--loglevel=erroris used.Platinum Sponsors
Gold Sponsors
v9.15.7: pnpm 9.15.7Compare Source
Patch Changes
pnpm self-updateshould not leave a directory with a broken pnpm installation if the installation fails.--config.prefix such as--@​scope:registry=https://scope.example.com/npm#9089.pnpm self-updateshould not read the pnpm settings from thepackage.jsonfile in the current working directory.pnpm update -ishould list only packages that have newer versions #9206.catalogssection of thepnpm-lock.yamlfile to be removed whendedupe-peer-dependents=falseon a filtered install. #9112Platinum Sponsors
Gold Sponsors
v9.15.6: pnpm 9.15.6Compare Source
Patch Changes
packageManagercannot start withv.pnpm-lock.yamlfile when using--fix-lockfileand--filter. #8639v9.15.5: pnpm 9.15.5Compare Source
Patch Changes
pnpm install, thepreprepareandpostpreparescripts of the project should be executed #8989.strip-ansiwith the built-inutil.stripVTControlCharacters#9009.Platinum Sponsors
Gold Sponsors
v9.15.4: pnpm 9.15.4Compare Source
Patch Changes
pnpm update --latest <pkg>updates only the specified package, withdedupe-peer-dependents=true.Platinum Sponsors
Gold Sponsors
v9.15.3: pnpm 9.15.3Compare Source
Patch Changes
pnpm update --filter <pattern> --latest <pkg>should only change the specified package for the specified workspace, whendedupe-peer-dependentsis set totrue#8877..DS_Storefile atpatch-commit#8922.pnpm patchis unable to bring back old patch without specifying@versionsuffix #8919.Platinum Sponsors
Gold Sponsors
v9.15.2: pnpm 9.15.2Compare Source
Patch Changes
publish/packerror with workspace dependencies with relative paths #8904. It was broken inv9.4.0(398472c).pnpm patchon Windows #7546.git ls-remoteworks via HTTPS #8906.Platinum Sponsors
Gold Sponsors
v9.15.1: pnpm 9.15.1Compare Source
Patch Changes
pnpm removeshould not link dependencies from the workspace, whenlink-workspace-packagesis set tofalse#7674.node_modulesshould not fail, when a dependency has itself in its own peer dependencies #8854.Platinum Sponsors
Gold 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 is behind base branch, 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.