-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update pnpm to v7.29.3 #15
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
❌ Deploy Preview for gztransfer failed.
|
renovate
bot
changed the title
chore(deps): update pnpm to v7
chore(deps): update pnpm to v7 - autoclosed
May 28, 2022
renovate
bot
changed the title
chore(deps): update pnpm to v7 - autoclosed
chore(deps): update pnpm to v7
May 29, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
May 29, 2022 11:42
58703cc
to
5804c2b
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7
chore(deps): update pnpm to v7.1.7
May 29, 2022
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.7
chore(deps): update pnpm to v7.1.7 - autoclosed
May 30, 2022
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.7 - autoclosed
chore(deps): update pnpm to v7.1.7
Jun 4, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 5, 2022 01:53
5804c2b
to
bfc3a5d
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.7
chore(deps): update pnpm to v7.1.8
Jun 5, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 6, 2022 03:09
bfc3a5d
to
7e9cb4d
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.8
chore(deps): update pnpm to v7.1.9
Jun 6, 2022
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.9
chore(deps): update pnpm to v7.1.9 - autoclosed
Jun 7, 2022
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.9 - autoclosed
chore(deps): update pnpm to v7.1.9
Jun 10, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 10, 2022 18:27
7e9cb4d
to
282cab9
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.1.9
chore(deps): update pnpm to v7.2.0
Jun 10, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
June 11, 2022 03:19
282cab9
to
0601991
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.2.0
chore(deps): update pnpm to v7.2.1
Jun 11, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 3, 2022 03:34
0f938ca
to
a81d3db
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.12.2
chore(deps): update pnpm to v7.13.0
Oct 3, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 4, 2022 11:11
a81d3db
to
0cc1a14
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.13.0
chore(deps): update pnpm to v7.13.1
Oct 4, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 5, 2022 23:22
0cc1a14
to
f75c327
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.13.1
chore(deps): update pnpm to v7.13.2
Oct 5, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 9, 2022 15:08
f75c327
to
514d6b6
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.13.2
chore(deps): update pnpm to v7.13.3
Oct 9, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 10, 2022 19:15
514d6b6
to
2f90369
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.13.3
chore(deps): update pnpm to v7.13.4
Oct 10, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 16, 2022 19:56
2f90369
to
0f4634b
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.13.4
chore(deps): update pnpm to v7.13.5
Oct 16, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 20, 2022 13:04
0f4634b
to
a10ea29
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.13.5
chore(deps): update pnpm to v7.13.6
Oct 20, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 22, 2022 15:34
a10ea29
to
0cb130b
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.13.6
chore(deps): update pnpm to v7.14.0
Oct 22, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
October 29, 2022 11:04
0cb130b
to
35ad114
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.14.0
chore(deps): update pnpm to v7.14.1
Oct 29, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
November 2, 2022 11:07
35ad114
to
56ddb10
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.14.1
chore(deps): update pnpm to v7.14.2
Nov 2, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
November 10, 2022 02:30
56ddb10
to
8d8befb
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.14.2
chore(deps): update pnpm to v7.15.0
Nov 10, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
November 20, 2022 15:17
8d8befb
to
7eb0032
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.15.0
chore(deps): update pnpm to v7.16.1
Nov 20, 2022
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 11, 2023 09:05
7eb0032
to
c70bfe1
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.16.1
chore(deps): update pnpm to v7.29.1
Mar 11, 2023
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
March 17, 2023 05:59
c70bfe1
to
132a4c5
Compare
renovate
bot
changed the title
chore(deps): update pnpm to v7.29.1
chore(deps): update pnpm to v7.29.3
Mar 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1.9
->7.29.3
Release Notes
pnpm/pnpm
v7.29.3
Compare Source
Patch Changes
node_modules/.pnpm/node_modules
directory through theNODE_PATH
env variable, then the command's ownnode_modules
directory #5176.extend-node-path
is set back totrue
by default. It was set tofalse
in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extendingNODE_PATH
. We have fixed the Jest issue with a different solution #6213.Our Gold Sponsors
Our Silver Sponsors
v7.29.2
Compare Source
v7.29.1
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.29.0
Compare Source
Minor Changes
A new setting is now supported:
dedupe-peer-dependents
.When this setting is set to
true
, packages with peer dependencies will be deduplicated after peers resolution.For instance, let's say we have a workspace with two projects and both of them have
webpack
in their dependencies.webpack
hasesbuild
in its optional peer dependencies, and one of the projects hasesbuild
in its dependencies. In this case, pnpm will link two instances ofwebpack
to thenode_modules/.pnpm
directory: one withesbuild
and another one without it:This makes sense because
webpack
is used in two projects, and one of the projects doesn't haveesbuild
, so the two projects cannot share the same instance ofwebpack
. However, this is not what most developers expect, especially since in a hoistednode_modules
, there would only be one instance ofwebpack
. Therefore, you may now use thededupe-peer-dependents
setting to deduplicatewebpack
when it has no conflicting peer dependencies (explanation at the end). In this case, if we setdedupe-peer-dependents
totrue
, both projects will use the samewebpack
instance, which is the one that hasesbuild
resolved:What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:
In this case, we cannot dedupe
webpack
aswebpack
hasreact
in its peer dependencies andreact
is resolved from two different versions in the context of the two projects.Patch Changes
The configuration added by
pnpm setup
should check if the pnpm home directory is already in the PATH before adding to the PATH.Before this change, this code was added to the shell:
Now this will be added:
Add
skipped
status in exec report summary when script is missing #6139.pnpm env -g
should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.Should not throw an error when local dependency use file protocol #6115.
Fix the incorrect error block when subproject has been patched #6183
Our Gold Sponsors
Our Silver Sponsors
v7.28.0
Compare Source
Minor Changes
--report-summary
forpnpm exec
andpnpm run
#6008.pnpm why --json
or--long
#6103.pnpm.peerDependencyRules.allowedVersions
package.json
option to support theparent>child
selector syntax. This syntax allows for extending specificpeerDependencies
#6108.Patch Changes
peerDependenciesMeta
and notpeerDependencies
,dependencies
, oroptionalDependencies
, the dependency's peers were not considered deterministically before.patch-commit
should auto apply patches in workspaces #6048pnpm config set
should write to the global config file by default #5877.Our Gold Sponsors
Our Silver Sponsors
v7.27.1
Compare Source
Patch Changes
store path
description to thepnpm
cli help.pnpm store prune
, when a tarball integrity error happens.strict-ssl
,ca
,key
, andcert
settings should work with HTTPS proxy servers #4689.Our Gold Sponsors
Our Silver Sponsors
v7.27.0
Compare Source
Minor Changes
resolution-mode
added:lowest-direct
. With this resolution mode direct dependencies will be resolved to their lowest versions. So if there isfoo@^1.1.0
in the dependencies, then1.1.0
will be installed, even if the latest version offoo
is1.2.0
.pnpm run /build:.*/
and execute the matched scripts with the RegExp #5871.Patch Changes
Fix version number replacing for namespaced workspace packages.
workspace:@​foo/bar@*
should be replaced withnpm:@​foo/bar@<version>
on publish #6052.When resolving dependencies, prefer versions that are already used in the root of the project. This is important to minimize the number of packages that will be nested during hoisting #6054.
Deduplicate direct dependencies.
Let's say there are two projects in the workspace that dependend on
foo
. One project hasfoo@1.0.0
in the dependencies while another one hasfoo@^1.0.0
in the dependencies. In this case,foo@1.0.0
should be installed to both projects as satisfies the version specs of both projects.Use Map rather than Object in
createPackageExtender
to prevent read the prototype property to native functionOur Gold Sponsors
Our Silver Sponsors
v7.26.3
Compare Source
Patch Changes
pnpm-lock.yaml
lockfile format #5976.Our Gold Sponsors
Our Silver Sponsors
v7.26.2
Compare Source
Patch Changes
pnpm audit
output for better readability #5981node-linker
is set tohoisted
#5992.Our Gold Sponsors
Our Silver Sponsors
v7.26.1
Compare Source
Patch Changes
node-linker
is set tohoisted
#5988.EMFILE: too many open files
by using graceful-fs for reading bin files of dependencies #5887.Our Gold Sponsors
Our Silver Sponsors
v7.26.0
Compare Source
Minor Changes
pnpm dedupe
command that removes dependencies from the lockfile by re-resolving the dependency graph. This work similar to yarn'syarn dedupe --strategy highest
command #5958Patch Changes
prepublishOnly
andprepublish
should not be executed onpnpm pack
#2941.Our Gold Sponsors
Our Silver Sponsors
v7.25.1
Compare Source
Patch Changes
pnpm audit
output #3073--force
option in thepnpm install
command #5932.prefer-symlinked-executables
istrue
#5946.pnpm install --fix-lockfile
should not fail if the package has no dependencies #5878.Our Gold Sponsors
Our Silver Sponsors
v7.25.0
Compare Source
Minor Changes
--ignore-existing
option #5632.extend-node-path
is set tofalse
, theNODE_PATH
environment variable is not set in the command shims #5910Patch Changes
prefer-symlinked-executables
is set totrue
#5913.node-linker=hoisted
.Our Gold Sponsors
Our Silver Sponsors
v7.24.3
Compare Source
Patch Changes
use-lockfile-v6
is not set totrue
.Our Gold Sponsors
Our Silver Sponsors