-
Notifications
You must be signed in to change notification settings - Fork 28
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 v9 #965
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/pnpm-9.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
April 29, 2024 21:28
0c6159b
to
d72c624
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
April 30, 2024 00:45
d72c624
to
54a9d5a
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
April 30, 2024 08:02
54a9d5a
to
1152ca1
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
April 30, 2024 12:24
1152ca1
to
d42caa0
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 1, 2024 00:33
d42caa0
to
38b1f48
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 1, 2024 18:46
38b1f48
to
14d01c2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 2, 2024 05:53
14d01c2
to
30ae7ef
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 3, 2024 10:17
30ae7ef
to
401e4a8
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 3, 2024 12:06
401e4a8
to
13af7ba
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 4, 2024 01:42
13af7ba
to
129c0f7
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 4, 2024 13:01
129c0f7
to
e6dcfd1
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 6, 2024 03:33
e6dcfd1
to
05d300b
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 6, 2024 10:28
05d300b
to
8345a69
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
May 7, 2024 02:14
8345a69
to
14acf71
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 20, 2024 00:54
af35c12
to
cca3ce9
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 20, 2024 14:28
cca3ce9
to
477811d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 22, 2024 13:08
477811d
to
a788f8d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 23, 2024 04:18
a788f8d
to
7717e37
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 23, 2024 14:12
7717e37
to
b3f844d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 23, 2024 23:10
b3f844d
to
d3dd7ef
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 24, 2024 04:37
d3dd7ef
to
f292a28
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 24, 2024 19:11
f292a28
to
fe1a7c9
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 26, 2024 09:28
fe1a7c9
to
83cc273
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 26, 2024 17:00
83cc273
to
e08a1ad
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 27, 2024 22:05
e08a1ad
to
d02dab3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 29, 2024 12:26
d02dab3
to
8022efc
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 30, 2024 03:08
8022efc
to
3f11b2e
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
September 30, 2024 18:35
3f11b2e
to
97ad190
Compare
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:
8.15.9
->9.11.0
Release Notes
pnpm/pnpm (pnpm)
v9.11.0
Compare Source
v9.10.0
: pnpm 9.10Compare Source
Minor Changes
Support for a new CLI flag,
--exclude-peers
, added to thelist
andwhy
commands. When--exclude-peers
is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.Added a new setting to
package.json
atpnpm.auditConfig.ignoreGhsas
for ignoring vulnerabilities by their GHSA code #6838.For instance:
Patch Changes
Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.9.0
Compare Source
v9.8.0
Compare Source
v9.7.1
Compare Source
v9.7.0
: pnpm 9.7Compare Source
Minor Changes
Added pnpm version management. If the
manage-package-manager-versions
setting is set totrue
, pnpm will switch to the version specified in thepackageManager
field ofpackage.json
#8363. This is the same field used by Corepack. Example:Added the ability to apply patch to all versions #8337.
If the key of
pnpm.patchedDependencies
is a package name without a version (e.g.pkg
), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version ofpkg
installed,pnpm patch pkg
and subsequentpnpm patch-commit $edit_dir
will create an entry namedpkg
inpnpm.patchedDependencies
. And pnpm will attempt to apply this patch to other versions ofpkg
in the future.Change the default edit dir location when running
pnpm patch
from a temporary directory tonode_modules/.pnpm_patches/pkg[@​version]
to allow the code editor to open the edit dir in the same file tree as the main project #8379.Substitute environment variables in config keys #6679.
Patch Changes
pnpm install
should runnode-gyp rebuild
if the project has abinding.gyp
file even if the project doesn't have an install script #8293.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.6.0
: pnpm 9.6Compare Source
Minor Changes
pnpm.executionEnv.nodeVersion
inpackage.json
) for running lifecycle scripts per each package in a workspace #6720.catalogs:
protocol #8303.Patch Changes
pnpm deploy
command now supports thecatalog:
protocol #8298.pnpm outdated
command now supports thecatalog:
protocol #8304.pnpm patch
withoutnode_modules/.modules.yaml
#8257.pnpm exec
command #7608.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.5.0
Compare Source
v9.4.0
Compare Source
v9.3.0
Compare Source
Minor Changes
peers-suffix-max-length
setting #8177.Patch Changes
reporter-hide-prefix
totrue
by default forpnpm exec
. In order to show prefix, the user now has to explicitly setreporter-hide-prefix=false
#8174.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.2.0
Compare Source
Minor Changes
package-manager-strict-version
is set totrue
, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field ofpackage.json
.Patch Changes
@yarnpkg/pnp
to the latest version, fixing issue withnode:
imports #8161.package.json
#8087.exec
now also streams prefixed output when--recursive
or--parallel
is specified just asrun
does #8065.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.1.4
Compare Source
v9.1.3
Compare Source
v9.1.2
Compare Source
Patch Changes
pnpm licenses
output are not misplaced anymore #8071.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.1.1
Compare Source
v9.1.0
Compare Source
v9.0.6
Compare Source
v9.0.5
Compare Source
v9.0.4
Compare Source
v9.0.3
Compare Source
v9.0.2
Compare Source
v9.0.1
Compare Source
v9.0.0
Compare Source
Major Changes
Node.js v16 support discontinued
If you still require Node.js 16, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the
@pnpm/exe
package.Configuration updates:
dedupe-injected-deps
: enabled by default.link-workspace-packages
: disabled by default. This means that by default, dependencies will be linked from workspace packages only when they are specified using the workspace protocol.hoist-workspace-packages
: enabled by default.enable-pre-post-scripts
: enabled by default.~/.local/state/pnpm
).package.json
file for apackageManager
field. If this field is present and specifies a different package manager or a different version of pnpm than the one you're currently using, pnpm will not proceed. This ensures that you're always using the correct package manager and version that the project requires.Lockfile changes:
Dependency resolution changes:
Related issue: #7444.
Related PR: #7606.
pnpm licenses list
prints license information of all versions of the same package in case different versions use different licenses. The format of thepnpm licenses list --json
output has been changed #7528.A new command added for printing completion code to the console:
pnpm completion [shell]
. The old command that modified the user's shell dotfiles has been removed #3083.When installing git-hosted dependencies, only pick the files that would be packed with the package #7638.
Minor Changes
It is now possible to install only a subdirectory from a Git repository.
For example,
pnpm add github:user/repo#path:packages/foo
will add a dependency from thepackages/foo
subdirectory.This new parameter may be combined with other supported parameters separated by
&
. For instance, the next command will install the same package from thedev
branch:pnpm add github:user/repo#dev&path:packages/bar
.Related issue: #4765.
Related PR: #7487.
node-gyp
updated to version 10.PowerShell completion support added #7597.
Support
node-options
option inside.npmrc
file when running scripts #7596.Added support for registry-scoped SSL configurations (cert, key, and ca). Three new settings supported:
<registryURL>:certfile
,<registryURL>:keyfile
, and<registryURL>:ca
. For instance:Related issue: #7427.
Related PR: #7626.
Add a field named
ignoredOptionalDependencies
. This is an array of strings. If an optional dependency has its name included in this array, it will be skipped #7714.The checksum of the
.pnpmfile.cjs
is saved into the lockfile. If the pnpmfile gets modified, the lockfile is reanalyzed to apply the changes #7662.Added cache for
pnpm dlx
#5277.Patch Changes
--lockfile-only
installation #1328.pnpm dlx
should not read settings from the currenConfiguration
📅 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 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 was generated by Mend Renovate. View the repository job log.