chore(deps): update pnpm to v7.8.0 #899
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.6.0
->7.8.0
Release Notes
pnpm/pnpm
v7.8.0
Compare Source
Minor Changes
publishConfig.directory
is set, only symlink it to other workspace projects ifpublishConfig.linkDirectory
is 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.1
Compare Source
Patch Changes
auto-install-peers
is set totrue
and the peer dependency is indevDependencies
oroptionalDependencies
#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.0
Compare Source
Minor Changes
Add experimental lockfile format that should merge conflict less in the
importers
section. Enabled by setting theuse-inline-specifiers-lockfile-format = true
feature 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.json
engines
field. Once this is set, older pnpm versions will throw on invalid lockfile versions.Add
publishDirectory
field to the lockfile and relink the project when it changes.verify-store-integrity=false
makes 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 deploy
should inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #5078.publishConfig.directory
set, dependent projects should install the project from that directory #3901.zshrc
in the right directory when a$ZDOTDIR
is set.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.6.0...v7.7.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.