⬆️ Update pnpm to v7.5.0 #112
Merged
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml |
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
bd550e4 to
d4a9838
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
d4a9838 to
cd0b0ba
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
cd0b0ba to
a526ec3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
a526ec3 to
ac8d058
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
ac8d058 to
aa1888f
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
247cbea to
09b46f2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
8ebe71d to
b5e2a6b
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
b5e2a6b to
5a9eaf2
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
5a9eaf2 to
9954d4e
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
acd07b6 to
e2051a3
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
e2051a3 to
69db714
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
69db714 to
7eec2c9
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
7eec2c9 to
9467931
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
9467931 to
61b28cc
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
61b28cc to
fa5fade
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
fa5fade to
0422f76
Compare
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
0422f76 to
81c393b
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:
7.0.1->7.5.0Release Notes
pnpm/pnpm
v7.5.0Compare Source
Minor Changes
A new value
rollingfor 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.npmrcwith the following content:Patch Changes
pnpm remove <pkg>should not fail in a workspace that has patches #4954pnpm env useshould 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.1Compare Source
Patch Changes
pnpm installin a workspace with patches should not fail when doing partial installation #4954.--lockfile-onlyis used. Even iffrozen-lockfileistrue#4951.patchedDependenciesfield topnpm-lock.yaml.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.4.0...v7.4.1
v7.4.0Compare Source
Minor Changes
Dependencies patching is possible via the
pnpm.patchedDependenciesfield 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:
{ "pnpm": { "patchedDependencies": { "eslint@1.0.0": "./patches/eslint@1.0.0.patch" } } }Two new commands added:
pnpm patchandpnpm 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.0that 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
patchedDependenciesfield inpackage.json:{ "pnpm": { "patchedDependencies": { "express@1.0.0": "patches/express@1.0.0.patch" } } }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
footo thedistdirectory in the root of the workspace:package-import-methodsupports a new option:clone-or-copy.New setting added:
include-workspace-root. When it is set totrue, therun,exec,add, andtestcommands will include the root package, when executed recursively #4906Patch Changes
Don't crash when
pnpm update --interactiveis cancelled with Ctrl+c.The
use-node-versionsetting 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 --fixshould 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.0Compare Source
Minor Changes
A new setting added:
pnpm.peerDependencyRules.allowAny.allowAnyis 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:{ "pnpm": { "peerDependencyRules": { "allowAny": ["@​babel/*", "eslint"] } } }The above setting will mute any warnings about peer dependency version mismatches related to
@babel/packages oreslint.The
pnpm.peerDependencyRules.ignoreMissingsetting may accept package name patterns. So you may ignore any missing@babel/*peer dependencies, for instance:{ "pnpm": { "peerDependencyRules": { "ignoreMissing": ["@​babel/*"] } } }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.1Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.2.0...v7.2.1
v7.2.0Compare Source
Minor Changes
A new setting is supported for ignoring specific deprecation messages:
pnpm.allowedDeprecatedVersions. The setting should be provided in thepnpmsection of the rootpackage.jsonfile. The below example will mute any deprecation warnings about therequestpackage and warnings aboutexpressv1:{ "pnpm": { "allowedDeprecatedVersions": { "request": "*", "express": "1" } } }Related issue: #4306
Related PR: #4864
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.9...v7.2.0
v7.1.9Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.8...v7.1.9
v7.1.8Compare Source
Patch Changes
package.jsonfile #4822.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.7...v7.1.8
v7.1.7Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.6...v7.1.7
v7.1.6Compare Source
Patch Changes
auto-install-peersis set totrue#4796.NODE_ENV=production pnpm install --devshould only install dev deps #4745.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.5...v7.1.6
v7.1.5Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.4...v7.1.5
v7.1.4Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.3...v7.1.4
v7.1.3Compare Source
Patch Changes
auto-install-peersis set totrue, automatically install missing peer dependencies without writing them topackage.jsonas dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #4776.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.2...v7.1.3
v7.1.2Compare Source
Patch Changes
pnpm setupshould not fail on Windows ifPNPM_HOMEis not yet in the system registry #4757pnpm dlxshouldn't modify the lockfile in the current working directory #4743.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.1...v7.1.2
v7.1.1Compare Source
Patch Changes
node_modules/.pnpmand inside the global store #4716pnpm create <pkg>should be passed to the executed create app package. Sopnpm create next-app --typescriptshould work`.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.0...v7.1.1
v7.1.0Compare Source
Minor Changes
libcfield inpackage.json#4454.Patch Changes
pnpm setupshould update the config of the current shell, not the preferred shell.pnpm setupshould not override the PNPM_HOME env variable, unless--forceis used.pnpm dlxshould print messages about installation to stderr #1698.pnpm dlxshould work with git-hosted packages. For example:pnpm dlx gengjiawen/envinfo#4714.pnpm run --streamshould prefix the output with directory #4702Our Sponsors
Full Changelog: pnpm/pnpm@v7.0.1...v7.1.0
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.
🔕 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.