-
Notifications
You must be signed in to change notification settings - Fork 112
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 #382
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
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
5 times, most recently
from
April 21, 2024 22:24
45f1bc3
to
bbe3218
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
April 24, 2024 17:18
bbe3218
to
6ff3891
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
May 12, 2024 22:10
89d1ea6
to
316ee2d
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
May 27, 2024 09:14
5b8c1c1
to
158ec31
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
June 5, 2024 17:30
51e14e8
to
e2fa3d5
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
June 10, 2024 15:12
e2fa3d5
to
26736a6
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
June 17, 2024 18:18
26736a6
to
b4cf9cf
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
June 30, 2024 12:40
7693bd8
to
a1ce9d2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
July 7, 2024 17:33
a1ce9d2
to
12d7cbb
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
July 23, 2024 03:32
dd634cb
to
5cb5291
Compare
commit: |
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
8 times, most recently
from
July 23, 2024 17:33
6531137
to
3d46475
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
August 7, 2024 22:35
cf41ae9
to
76001d2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
3 times, most recently
from
August 15, 2024 20:56
308cf1c
to
b9918b5
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
August 26, 2024 16:32
a383e5b
to
26ff12a
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
9 times, most recently
from
September 4, 2024 10:18
e0533b1
to
d15546c
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
2 times, most recently
from
September 11, 2024 01:49
9d486a9
to
de76eb1
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
4 times, most recently
from
September 24, 2024 08:43
7b43495
to
2a18658
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
4 times, most recently
from
October 2, 2024 13:51
21e0fd8
to
9e5236e
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
October 7, 2024 16:30
9e5236e
to
3be7e28
Compare
renovate
bot
force-pushed
the
renovate/pnpm-9.x
branch
from
October 16, 2024 15:44
3be7e28
to
ca99d8e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.12.2
Release Notes
pnpm/pnpm (pnpm)
v9.12.2
Compare Source
v9.12.1
: pnpm 9.12.1Compare Source
Patch Changes
pnpm update --latest
should not update the automatically installed peer dependencies #6657.pnpm publish
should be able to publish from a local tarball #7950.EBUSY
errors caused by creating symlinks in paralleldlx
processes #8604.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
v9.12.0
: pnpm 9.12Compare Source
Minor Changes
Fix peer dependency resolution dead lock #8570. This change might change some of the keys in the
snapshots
field insidepnpm-lock.yaml
but it should happen very rarely.pnpm outdated
command supports now a--sort-by=name
option for sorting outdated dependencies by package name #8523.Added the ability for
overrides
to remove dependencies by specifying"-"
as the field value #8572. For example, to removelodash
from the dependencies, use this configuration inpackage.json
:Patch Changes
pnpm list --json pkg
showed"private": false
for a private package #8519.libc
that differ frompnpm.supportedArchitectures.libc
are not downloaded #7362.ENOENT
errors caused by runningstore prune
in parallel #8586.pnpm bugs
#8596.Platinum Sponsors
Gold Sponsors
Our Silver Sponsors
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