chore(deps): update pnpm to v7.9.0 #34
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}
|
Kudos, SonarCloud Quality Gate passed!
|
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.0->7.9.0Release Notes
pnpm/pnpm
v7.9.0Compare Source
Minor Changes
ignore-dep-scriptsistrue, ignore scripts of dependencies but run the scripts of the project.ignore-compatibility-dbis set totrue, the compatibility database will not be used to patch dependencies #5132.Patch Changes
pnpm setupshould suggest users to source the config instead of restarting the terminal.binthat points to an.exefile on Windows #5159.verify-store-integrityis set tofalse.Our Gold Sponsors
v7.8.0Compare Source
Minor Changes
publishConfig.directoryis set, only symlink it to other workspace projects ifpublishConfig.linkDirectoryis set totrue. Otherwise, only use it for publishing #5115.Patch Changes
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.7.1...v7.8.0
v7.7.1Compare Source
Patch Changes
auto-install-peersis set totrueand the peer dependency is indevDependenciesoroptionalDependencies#5080.workspace:^orworkspace:~version specs are used in a workspace.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.7.0...v7.7.1
v7.7.0Compare Source
Minor Changes
Add experimental lockfile format that should merge conflict less in the
importerssection. Enabled by setting theuse-inline-specifiers-lockfile-format = truefeature flag in.npmrc.If this feature flag is committed to a repo, we recommend setting the minimum allowed version of pnpm to this release in the
package.jsonenginesfield. Once this is set, older pnpm versions will throw on invalid lockfile versions.Add
publishDirectoryfield to the lockfile and relink the project when it changes.verify-store-integrity=falsemakes pnpm skip checking the integrities of files in the global content-addressable store.Allow to set
only-built-dependencies[]through.npmrc.Patch Changes
publishConfig.directory) #3901.pnpm deployshould inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #5078.publishConfig.directoryset, dependent projects should install the project from that directory #3901.zshrcin the right directory when a$ZDOTDIRis set.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.6.0...v7.7.0
v7.6.0Compare Source
Minor Changes
A new setting supported:
prefer-symlinked-executables. Whentrue, pnpm will create symlinks to executables innode_modules/.bininstead of command shims (but on POSIX systems only).This setting is
trueby default whennode-linkeris set tohoisted.Related issue: #4782.
When
lockfile-include-tarball-urlis set totrue, every entry inpnpm-lock.yamlwill contain the full URL to the package's tarball #5054.Patch Changes
pnpm deployshould include all dependencies by default #5035.Don't print warnings about file verifications. Just print info messages instead.
pnpm publish --helpshould print the--recursiveand--filteroptions #5019.It should be possible to run exec/run/dlx with the
--use-node-versionoption.pnpm deployshould not modify the lockfile #5071pnpm deployshould not fail in CI #5071When
auto-install-peersis set totrue, automatically install direct peer dependencies #5028.So if your project the next manifest:
{ "dependencies": { "lodash": "^4.17.21" }, "peerDependencies": { "react": "^18.2.0" } }pnpm will install both lodash and react as a regular dependencies.
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.2...v7.6.0
v7.5.2Compare Source
Patch Changes
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.1...v7.5.2
v7.5.1Compare Source
Patch Changes
node_modules#4988.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.0...v7.5.1
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": { "[email protected]": "./patches/[email protected]" } } }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
[email protected]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/[email protected].Also, it will reference this new patch file from the
patchedDependenciesfield inpackage.json:{ "pnpm": { "patchedDependencies": { "[email protected]": "patches/[email protected]" } } }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.4[Compare Source](https://github.com/pnpm/pnpm/compare/v7.1.3...v7.1.4
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.