-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
build(deps): update pnpm to v10.6.2 #4917
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/pnpm-10.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
+4
−4
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 ↗︎
|
a6cd2b9
to
27aaafa
Compare
27aaafa
to
63534a5
Compare
63534a5
to
994d55c
Compare
994d55c
to
3471a9e
Compare
3471a9e
to
73e86bb
Compare
73e86bb
to
67966b5
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:
10.4.1
->10.6.2
Release Notes
pnpm/pnpm (pnpm)
v10.6.2
Compare Source
Patch Changes
pnpm self-update
should always update the version in thepackageManager
field ofpackage.json
.pnpm patch-commit
will now use the same filesystem as the store directory to compare and create patch files.--loglevel=error
is used.peerDependencyRules
should be set inpnpm-workspace.yaml
to take effect.v10.6.1
Compare Source
Patch Changes
--silent
reporting is used.--loglevel
is set toerror
, don't show installation summary, execution time, and big tarball download progress.package.json
#9226.approve-builds
command, if package.json containsonlyBuiltDependencies
orignoredBuiltDependencies
, the selected dependency package will continue to be written intopackage.json
.v10.6.0
Compare Source
Minor Changes
pnpm-workspace.yaml
can now hold all the settings that.npmrc
accepts. The settings should use camelCase #9211.pnpm-workspace.yaml
example:Projects using a
file:
dependency on a local tarball file (i.e..tgz
,.tar.gz
,.tar
) will see a performance improvement during installation. Previously, using afile:
dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.Patch Changes
pnpm self-update
should not leave a directory with a broken pnpm installation if the installation fails.fast-glob
replace withtinyglobby
to reduce the size of the pnpm CLI dependencies #9169.pnpm deploy
should not remove fields from the deployed package'spackage.json
file #9215.pnpm self-update
should not read the pnpm settings from thepackage.json
file in the current working directory.pnpm deploy
creating apackage.json
without theimports
andlicense
field #9193.pnpm update -i
should list only packages that have newer versions #9206.catalogs
section of thepnpm-lock.yaml
file to be removed whendedupe-peer-dependents=false
on a filtered install. #9112v10.5.2
Compare Source
Patch Changes
pnpm config set
command should change the global.npmrc
file by default.This was a regression introduced by #9151 and shipped in pnpm v10.5.0.
v10.5.1
Compare Source
Patch Changes
pnpm-workspaces.yaml
orpnpm-workspaces.yml
file is found instead of apnpm-workspace.yaml
#9170.pnpm-workspace.yaml
by thepnpm approve-builds
command #9168.package.json
#9163overrides
inpnpm-workspace.yaml
should work.pnpm dlx
should ignore settings from thepackage.json
file in the current working directory #9178.v10.5.0
Compare Source
Minor Changes
Allow to set the "pnpm" settings from
package.json
via thepnpm-workspace.yaml
file #9121.Added support for automatically syncing files of injected workspace packages after
pnpm run
#9081. Use thesync-injected-deps-after-scripts
setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a.npmrc
file at the root of the workspace. Example:The
packages
field inpnpm-workspace.yaml
became optional.Patch Changes
pnpm link
with no parameters should work as if--global
is specified #9151.--config.
prefix such as--@​scope:registry=https://scope.example.com/npm
#9089.pnpm link <path>
should calculate relative path from the root of the workspace directory #9132.pnpm-lock.yaml
file when using--fix-lockfile
and--filter
. #8639Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.