chore(deps): update pnpm to v7.17.0 #12
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}
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
9989b37
to
b9fa20f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
b9fa20f
to
3b6552c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
3b6552c
to
4b5ceb8
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
2 times, most recently
from
f94b4cd
to
7cfdbd3
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
7cfdbd3
to
8f3b458
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
8f3b458
to
2d2f116
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pnpm-7.x
branch
from
2d2f116
to
210bf17
Compare
renovate
bot
changed the title
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.1.0->7.17.0Release Notes
pnpm/pnpm
v7.17.0Compare Source
Minor Changes
pnpm licenses list, which displays the licenses of the packages #2825Patch Changes
pnpm update --latest !fooshould not update anything if the only dependency in the project is the ignored one #5643.pnpm auditshould send the versions of workspace projects for audit.pnpm.updateConfig.ignoreDependenciessetting should work with multiple dependencies in the array #5639.Our Gold Sponsors
Our Silver Sponsors
v7.16.1Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.16.0Compare Source
Minor Changes
pnpm env listto list global or remote Node.js versions #5546.Patch Changes
.npmrcfiles in subdirectories inside a workspace #2570.Our Gold Sponsors
Our Silver Sponsors
v7.15.0Compare Source
Minor Changes
Support
--format=jsonoption to output outdated packages in JSON format withoutdatedcommand #2705.pnpm outdated --format=json #or pnpm outdated --jsonA new setting supported for ignoring vulnerabilities by their CVEs. The ignored CVEs may be listed in the
pnpm.auditConfig.ignoreCvesfield ofpackage.json. For instance:{ "pnpm": { "auditConfig": { "ignoreCves": [ "CVE-2019-10742", "CVE-2020-28168", "CVE-2021-3749", "CVE-2020-7598" ] } } }Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.14.2Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.14.1Compare Source
Patch Changes
pnpm list --long --jsonshould print licenses and authors of packages #5533..pnpmfile.cjs.pnpm dlxcommand.package.jsonhas a workspaces field but there is nopnpm-workspace.yamlfile #5363.Our Gold Sponsors
Our Silver Sponsors
v7.14.0Compare Source
Minor Changes
pnpm doctorcommand to do checks for known common issuesPatch Changes
Ignore the
always-authsetting.pnpm will never reuse the registry auth token for requesting the package tarball, if the package tarball is hosted on a different domain.
So, for example, if your registry is at
https://company.registry.com/but the tarballs are hosted athttps://tarballs.com/, then you will have to configure the auth token for both domains in your.npmrc:Our Gold Sponsors
Our Silver Sponsors
v7.13.6Compare Source
Patch Changes
@pnpm/npm-confto remove annoying builtin warning #5518.pnpm link --global <pkg>should not change the type of the dependency #5478.pnpm outdatedcommand fails, print in which directory it failed.Our Gold Sponsors
Our Silver Sponsors
v7.13.5Compare Source
Patch Changes
pnpm outdatedshould work when the package tarballs are hosted on a domain that differs from the registry's domain #5492.strict-peer-dependenciesis set tofalseby default.Our Gold Sponsors
Our Silver Sponsors
v7.13.4Compare Source
Patch Changes
pnpm link <pkg> --globalshould work when a custom target directory is specified with the--dirCLI option #5473.Our Gold Sponsors
Our Silver Sponsors
v7.13.3Compare Source
Patch Changes
auto-install-peersis set totrueand installation is done on a workspace with that has the same dependencies in multiple projects #5454.pnpm link --help#5461.install,update,add, andremove#1021.pnpm pack, when a custom destination directory is used #5471.Our Gold Sponsors
Our Silver Sponsors
v7.13.2Compare Source
Patch Changes
When linking commands to a directory, remove any .exe files that are already present in that target directory by the same name.
This fixes an issue with pnpm global update on Windows. If pnpm was installed with the standalone script and then updated with pnpm using
pnpm add --global pnpm, the exe file initially created by the standalone script should be removed.When a direct dependency fails to resolve, print the path to the project directory in the error message.
pnpm patch-commitshould work when the patch directory is specified with a trailing slash #5449.Our Gold Sponsors
Our Silver Sponsors
v7.13.1Compare Source
Patch Changes
pnpm update --interactiveshould not list dependencies ignored via thepnpm.updateConfig.ignoreDependenciessetting.Our Gold Sponsors
Our Silver Sponsors
v7.13.0Compare Source
Minor Changes
Ignore packages listed in
package.json>pnpm.updateConfig.ignoreDependenciesfields on update/outdated command #5358For instance, if you don't want
webpackautomatically to be updated when you runpnpm update --latest, put this to yourpackage.json:{ "pnpm": { "updateConfig": { "ignoreDependencies": ["webpack"] } } }Patterns are also supported, so you may ignore for instance any packages from a scope:
@babel/*.It is possible now to update all dependencies except the listed ones using
!. For instance, update all dependencies, exceptlodash:It also works with pattends, for instance:
And it may be combined with other patterns:
Patch Changes
Hooks should be applied on
pnpm deploy#5306.Stop
--filter-prodoption to run command on all the projects when used on workspace.--filter-prodoption now only filter fromdependenciesand omitdevDependenciesinstead of including all the packages when used on workspace. So what was happening is that if you use--filter-prodon workspace root like this:it was printing all the package of workspace, where it should only print the package name of itself and packages where it has been added as
dependency(not asdevDependencies)Don't override the root dependency when auto installing peer dependencies #5412.
Our Gold Sponsors
Our Silver Sponsors
What's Changed
package.json > pnpm.updateConfig.ignoreDependencieson update/outdated commands by @Shinyaigehttps://github.com/pnpm/pnpm/pull/5408l/5408New Contributors
Full Changelog: pnpm/pnpm@v7.12.2...v7.13.0
v7.12.2Compare Source
Patch Changes
pnpm link --globalshould work with the--dir=<path>option #5371.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.12.1...v7.12.2
v7.12.1Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
Full Changelog: pnpm/pnpm@v7.12.0...v7.12.1
v7.12.0Compare Source
Minor Changes
A new setting supported in the pnpm section of the
package.jsonfile:allowNonAppliedPatches. When it is set totrue, non-applied patches will not cause an error, just a warning will be printed. For example:{ "name": "foo", "version": "1.0.0", "pnpm": { "patchedDependencies": { "express@4.18.1": "patches/express@4.18.1.patch" }, "allowNonAppliedPatches": true } }Now it is possible to exclude packages from hoisting by prepending a
!to the pattern. This works with both thehoist-patternandpublic-hoist-patternsettings. For instance:Ref #5272
Patch Changes
pnpm patchshould work on files that don't have an end of line #5320.pnpm patchusing a custom--edit-dir.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
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.