chore(deps): update pnpm to v7.9.0

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	7.6.0 -> 7.9.0

---

Release Notes

pnpm/pnpm

v7.9.0

Compare Source

Minor Changes

• When ignore-dep-scripts is true, ignore scripts of dependencies but run the scripts of the project.
• When ignore-compatibility-db is set to true, the compatibility database will not be used to patch dependencies #​5132.
• Print the versions of packages in peer dependency warnings and errors.
• Support a new hook for passing a custom package importer to the store controller.

Patch Changes

• Don't print the same deprecation warning multiple times.
• On POSIX pnpm setup should suggest users to source the config instead of restarting the terminal.
• Installing a package with bin that points to an .exe file on Windows #​5159.
• Fix bug where the package manifest was not resolved if verify-store-integrity is set to false.
• Fix sorting of keys in lockfile to make it more deterministic and prevent unnecessary churn in the lockfile #​5151.
• Don't create a separate bundle for pnpx.

Our Gold Sponsors

#### Our Silver Sponsors

v7.8.0

Compare Source

Minor Changes

• When publishConfig.directory is set, only symlink it to other workspace projects if publishConfig.linkDirectory is set to true. Otherwise, only use it for publishing #​5115.

Patch Changes

• Don't incorrectly identify a lockfile out-of-date when the package has a publishConfig.directory field #​5124.
• Don't crash when a config file contains a setting with an env variable that doesn't exist #​5093.

Our Gold Sponsors

#### Our Silver Sponsors #### What's Changed * fix: don't incorrectly identify a lockfile out-of-date by @​zkochan in https://github.com/pnpm/pnpm/pull/5126 * feat: publishConfig.linkDirectory by @​zkochan in https://github.com/pnpm/pnpm/pull/5125 * fix: don't crash on a .npmrc with missing env var by @​zkochan in https://github.com/pnpm/pnpm/pull/5127 * chore: fix typo by @​LuciNyan in https://github.com/pnpm/pnpm/pull/5128 #### New Contributors * @​LuciNyan made their first contribution in https://github.com/pnpm/pnpm/pull/5128

Full Changelog: https://github.com/pnpm/pnpm/compare/v7.7.1...v7.8.0

v7.7.1

Compare Source

Patch Changes

• pnpm should not consider a lockfile out-of-date if auto-install-peers is set to true and the peer dependency is in devDependencies or optionalDependencies #​5080.
• Don't incorrectly consider a lockfile out-of-date when workspace:^ or workspace:~ version specs are used in a workspace.

Our Gold Sponsors

#### Our Silver Sponsors #### What's Changed * fix: frozen install in a project with peer deps and `auto-install-peers=true` by @​zkochan in https://github.com/pnpm/pnpm/pull/5120 * fix: don't incorrectly consider a lockfile to be out-of-date by @​zkochan in https://github.com/pnpm/pnpm/pull/5121

Full Changelog: https://github.com/pnpm/pnpm/compare/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 the use-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

• It should be possible to publish a package with local dependencies from a custom publish directory (set via publishConfig.directory) #​3901.
• pnpm deploy should inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #​5078.
• When a project in a workspace has a publishConfig.directory set, dependent projects should install the project from that directory #​3901
• pnpm deploy: accept absolute paths and use cwd instead of workspaceDir for deploy target directory #​4980.
• pnpm setup should update .zshrc in the right directory when a $ZDOTDIR is set.

Our Gold Sponsors

#### Our Silver Sponsors #### What's Changed * fix(deploy): inject all types of deps by @​zkochan in https://github.com/pnpm/pnpm/pull/5084 * fix(make-dedicated-lockfile): prepublishOnly script is automatically … by @​zkochan in https://github.com/pnpm/pnpm/pull/5083 * fix: symlink a workspace pkg correctly, when it has a custom publish dir by @​zkochan in https://github.com/pnpm/pnpm/pull/5089 * feat: add experimental use-inline-specifiers-lockfile-format by @​gluxon in https://github.com/pnpm/pnpm/pull/5091 * fix: plugin-commands-deploy use path resolve on deploy target dir by @​AWare in https://github.com/pnpm/pnpm/pull/5026 * fix: relink the project when its publish directory changes by @​zkochan in https://github.com/pnpm/pnpm/pull/5109 * fix: don't include specifiers field in new experimental lockfile format by @​zkochan in https://github.com/pnpm/pnpm/pull/5110 * feat: verify-store-integrity by @​zkochan in https://github.com/pnpm/pnpm/pull/5112 #### New Contributors * @​AWare made their first contribution in https://github.com/pnpm/pnpm/pull/5026

Full Changelog: https://github.com/pnpm/pnpm/compare/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.

---

• [ ] If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate[bot]]

⚠ Artifact update problem

Renovate 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:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

installing v2 tool pnpm v7.7.0
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 1 package in 3s
linking tool pnpm v7.7.0
7.7.0
Installed v2 /usr/local/buildpack/tools/v2/pnpm.sh in 5 seconds
Scope: all 4 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 34, reused 0, downloaded 8, added 0
Progress: resolved 39, reused 0, downloaded 15, added 0
Progress: resolved 43, reused 0, downloaded 19, added 0
Progress: resolved 44, reused 0, downloaded 19, added 0
Progress: resolved 45, reused 0, downloaded 20, added 0
Progress: resolved 45, reused 0, downloaded 21, added 0
Progress: resolved 55, reused 0, downloaded 25, added 0
Progress: resolved 56, reused 0, downloaded 25, added 0
Progress: resolved 56, reused 0, downloaded 27, added 0
Progress: resolved 57, reused 0, downloaded 27, added 0
Progress: resolved 97, reused 0, downloaded 32, added 0
Progress: resolved 155, reused 0, downloaded 47, added 0
Progress: resolved 194, reused 0, downloaded 69, added 0
Progress: resolved 235, reused 0, downloaded 83, added 0
Progress: resolved 247, reused 0, downloaded 97, added 0
Progress: resolved 264, reused 0, downloaded 111, added 0
Progress: resolved 280, reused 0, downloaded 128, added 0
Progress: resolved 286, reused 0, downloaded 135, added 0
Progress: resolved 324, reused 0, downloaded 152, added 0
Progress: resolved 412, reused 0, downloaded 174, added 0
Progress: resolved 484, reused 0, downloaded 207, added 0
Progress: resolved 575, reused 0, downloaded 240, added 0
Progress: resolved 615, reused 0, downloaded 251, added 0
Progress: resolved 655, reused 0, downloaded 261, added 0
Progress: resolved 695, reused 0, downloaded 289, added 0
.                                        |  WARN  deprecated [email protected]
Progress: resolved 733, reused 0, downloaded 313, added 0
Progress: resolved 820, reused 0, downloaded 346, added 0
Progress: resolved 874, reused 0, downloaded 378, added 0
Progress: resolved 911, reused 0, downloaded 398, added 0
Progress: resolved 926, reused 0, downloaded 408, added 0
Progress: resolved 979, reused 0, downloaded 430, added 0
Progress: resolved 1088, reused 0, downloaded 464, added 0
Progress: resolved 1211, reused 0, downloaded 496, added 0
Progress: resolved 1276, reused 0, downloaded 520, added 0
Progress: resolved 1351, reused 0, downloaded 555, added 0
Progress: resolved 1432, reused 0, downloaded 582, added 0
Progress: resolved 1590, reused 0, downloaded 618, added 0
Progress: resolved 1643, reused 0, downloaded 651, added 0
Progress: resolved 1646, reused 0, downloaded 653, added 0
Progress: resolved 1651, reused 0, downloaded 655, added 0
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

packages/core
└─┬ ts-jest
  └── ✕ unmet peer @types/jest@^27.0.0: found 28.1.0

packages/rollup
└─┬ ts-jest
  └── ✕ unmet peer @types/jest@^27.0.0: found 28.1.0

packages/vite
└─┬ ts-jest
  └── ✕ unmet peer @types/jest@^27.0.0: found 28.1.0

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 7c5d77438d09308643bde2104a37bf0bb94e3b21

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov[bot]]

Codecov Report

Merging #361 (7c5d774) into main (bf36008) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #361   +/-   ##
=======================================
  Coverage   94.47%   94.47%           
=======================================
  Files          30       30           
  Lines         434      434           
  Branches      111      111           
=======================================
  Hits          410      410           
  Misses         24       24           

Flag	Coverage Δ
imagetools-core	97.64% <ø> (ø)
rollup-plugin-imagetools	98.30% <ø> (ø)
vite-imagetools	79.48% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.