chore(deps): lock file maintenance non-major updates and lockfile maintenance(auto merge) - autoclosed #57
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:
20.8.10
->20.10.4
20.9.0
->20.10.0
8.10.2
->8.12.0
🔧 This Pull Request updates lock files to use the latest dependency versions.
Release Notes
nodejs/node (node)
v20.10.0
Compare Source
pnpm/pnpm (pnpm)
v8.12.0
Compare Source
Minor Changes
Patch Changes
dedupe-direct-deps
is set totrue
, commands of dependencies should be deduplicated #7359.Our Gold Sponsors
Our Silver Sponsors
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
v8.10.5
Compare Source
Patch Changes
pnpm-workspace.yaml
file #7307.Our Gold Sponsors
Our Silver Sponsors
v8.10.4
Compare Source
Patch Changes
node-linker
was set tohoisted
#6227.Our Gold Sponsors
Our Silver Sponsors
v8.10.3
Compare Source
Patch Changes
(Important) Increased the default amount of allowed concurrent network request on systems that have more than 16 CPUs #7285.
pnpm patch
should reuse existing patch whenshared-workspace-file=false
#7252.Don't retry fetching missing packages, since the retries will never work #7276.
When using
pnpm store prune --force
alien directories are removed from the store #7272.Downgraded
npm-packlist
because the newer version significantly slows down the installation of local directory dependencies, making it unbearably slow.npm-packlist
was upgraded in this PR to fix #6997. We added our own file deduplication to fix the issue of duplicate file entries.Fixed a performance regression on running installation on a project with an up to date lockfile #7297.
Throw an error on invalid
pnpm-workspace.yaml
file #7273.Our Gold Sponsors
Our Silver Sponsors
Configuration
📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.