chore(deps): update all non-major dependencies #63
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.11.2
->^7.11.3
7.2.0
->7.5.0
Release Notes
bcoe/c8
v7.11.3
Compare Source
pnpm/pnpm
v7.5.0
Compare Source
Minor Changes
A new value
rolling
for optionsave-workspace-protocol
. When selected, pnpm will save workspace versions using a rolling alias (e.g."foo": "workspace:^"
) instead of pinning the current version number (e.g."foo": "workspace:^1.0.0"
). Usage example, in the root of your workspace, create a.npmrc
with the following content:Patch Changes
pnpm remove <pkg>
should not fail in a workspace that has patches #4954pnpm env use
should throw an error on a system that use the MUSL libc.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0
v7.4.1
Compare Source
Patch Changes
pnpm install
in a workspace with patches should not fail when doing partial installation #4954.--lockfile-only
is used. Even iffrozen-lockfile
istrue
#4951.patchedDependencies
field topnpm-lock.yaml
.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.4.0...v7.4.1
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
v7.3.0
Compare Source
Minor Changes
A new setting added:
pnpm.peerDependencyRules.allowAny
.allowAny
is an array of package name patterns, any peer dependency matching the pattern will be resolved from any version, regardless of the range specified inpeerDependencies
. For instance:The above setting will mute any warnings about peer dependency version mismatches related to
@babel/
packages oreslint
.The
pnpm.peerDependencyRules.ignoreMissing
setting may accept package name patterns. So you may ignore any missing@babel/*
peer dependencies, for instance:Experimental. New settings added:
use-git-branch-lockfile
,merge-git-branch-lockfiles
,merge-git-branch-lockfiles-branch-pattern
#4475.Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.2.1...v7.3.0
v7.2.1
Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.2.0...v7.2.1
Configuration
📅 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.