chore(deps): update pnpm to v7.4.0 #176
Merged
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.3.0
->7.4.0
Release Notes
pnpm/pnpm
v7.4.0
Compare Source
Minor Changes
Dependencies patching is possible via the
pnpm.patchedDependencies
field of thepackage.json
.To patch a package, the package name, exact version, and the relative path to the patch file should be specified. For instance:
Two new commands added:
pnpm patch
andpnpm patch-commit
.pnpm patch <pkg>
prepares a package for patching. For instance, if you want to patch express v1, run:pnpm will create a temporary directory with
express@1.0.0
that you can modify with your changes.Once you are read with your changes, run:
This will create a patch file and write it to
<project>/patches/express@1.0.0.patch
.Also, it will reference this new patch file from the
patchedDependencies
field inpackage.json
:A new experimental command added:
pnpm deploy
. The deploy command takes copies a project from a workspace and installs all of its production dependencies (even if some of those dependencies are other projects from the workspace).For example, the new command will deploy the project named
foo
to thedist
directory in the root of the workspace:package-import-method
supports a new option:clone-or-copy
.New setting added:
include-workspace-root
. When it is set totrue
, therun
,exec
,add
, andtest
commands will include the root package, when executed recursively #4906Patch Changes
Don't crash when
pnpm update --interactive
is cancelled with Ctrl+c.The
use-node-version
setting should work with prerelease Node.js versions. For instance:Return early when the lockfile is up-to-date.
Resolve native workspace path for case-insensitive file systems #4904.
Don't link local dev dependencies, when prod dependencies should only be installed.
pnpm audit --fix
should not add an override for a vulnerable package that has no fixes released.Update the compatibility database.
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.3.0...v7.4.0
Configuration
📅 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 has been generated by Mend Renovate. View repository job log here.