chore(deps): update pnpm to v8.11.0 #365
No reviewers
Labels
No labels
API
bug
can't reproduce
confirmed
dependencies
documentation
duplicate
enhancement
feature
good first issue
help wanted
invalid
performance
question
to be confirmed
waiting for feedback
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: dungeonslayers/ds4#365
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/pnpm-8.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
8.10.5
->8.11.0
Release Notes
pnpm/pnpm (pnpm)
v8.11.0
Compare Source
Minor Changes
(IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain
/<pkg_name>@​<pkg_version
, not<domain>/<pkg_name>@​<pkg_version>
.This change is a fix to avoid the same package from being added to
node_modules/.pnpm
multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.
Related PR: #7318.
Patch Changes
pnpm add a-module-already-in-dev-deps
will show a message to notice the user that the package was not moved to "dependencies" #926.Our Gold Sponsors
Our Silver Sponsors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Renovate Bot.