chore(deps): update pnpm to v8 - autoclosed #14
Closed
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:
>=7
->>=8.6.6
7.25.0
->8.6.6
Release Notes
pnpm/pnpm (pnpm)
v8.6.6
Compare Source
Patch Changes
package.json
should not fail, when the dependency is read from cache #6721.preferredVersions
object #6735resolvePeersOfNode
#6736preferredVersions
inresolveDependenciesOfImporters
#6748isEmpty
usages #6753splitNodeId
, fix invalidnodeId
#6755Our Gold Sponsors
Our Silver Sponsors
v8.6.5
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v8.6.4
Compare Source
Patch Changes
.npmrc
file #6354.Our Gold Sponsors
Our Silver Sponsors
v8.6.3
Compare Source
Patch Changes
APPDATA
env variable is not set on Windows #6659.node-linker
is set tohoisted
#6680.pnpm update --global --latest
should work #3779.pnpm license ls
should work even when there is a patched git protocol dependency #6595Our Gold Sponsors
Our Silver Sponsors
v8.6.2
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v8.6.1
Compare Source
Patch Changes
When
dedupe-peer-dependents
is enabled (default), use the path (not id) to determine compatibility.When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication.
Resolves: #6605
Some minor performance improvements by removing await from loops #6617.
Our Gold Sponsors
Our Silver Sponsors
v8.6.0
Compare Source
Minor Changes
Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.
A new field will now be present in the lockfile:
settings
. It will store the values of two settings:autoInstallPeers
andexcludeLinksFromLockfile
. If someone tries to perform afrozen-lockfile
installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.The lockfile format version is bumped from v6.0 to v6.1.
Related PR: #6557
Related issue: #6312
A new setting,
exclude-links-from-lockfile
, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.This setting was primarily added for use by Bit CLI, which links core aspects to
node_modules
from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.Patch Changes
npm:foo@1.0.0
becomesnpm:foo@1.1.0
.workspace:
protocol is not found in the workspace #4477.pnpm rebuild
should not fail whennode-linker
is set tohoisted
and there are skipped optional dependencies #6553.Our Gold Sponsors
Our Silver Sponsors
v8.5.1
Compare Source
Patch Changes
package.json
file(s), print out what are the differences #6536.Our Gold Sponsors
Our Silver Sponsors
v8.5.0
Compare Source
Minor Changes
pnpm patch-remove
command added #6521.Patch Changes
pnpm link -g <pkg-name>
should not modify thepackage.json
file #4341.node_modules
directory #6510.engines
field should match prerelease versions #6509.Our Gold Sponsors
Our Silver Sponsors
v8.4.0
Compare Source
Minor Changes
pnpm publish
supports the--provenance
CLI option #6435.Patch Changes
node-linker
is set tohoisted
6486.node_modules
directory unless the--force
option is passed.node_modules
folder with a.modules.yaml
file if there are no dependencies insidenode_modules
.Our Gold Sponsors
Our Silver Sponsors
v8.3.1
Compare Source
Patch Changes
node-fetch
to fix an error that happens on Node.js 20 #6424.Our Gold Sponsors
Our Silver Sponsors
v8.3.0
Compare Source
Minor Changes
pnpm pack
command using thepack-gzip-level
setting #6393.--check
flag topnpm dedupe
. No changes will be made tonode_modules
or the lockfile. Exits with a non-zero status code if changes are possible.pnpm install --resolution-only
re-runs resolution to print out any peer dependency issues #6411.Patch Changes
publishConfig.directory
of an injected workspace dependency does not exist #6396.Our Gold Sponsors
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.