chore(deps): update pnpm to v8.9.2

renovate[bot] commented 11 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`8.8.0` -> `8.9.2`

Release Notes

pnpm/pnpm (pnpm)

### [`v8.9.2`](https://togithub.com/pnpm/pnpm/releases/tag/v8.9.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.9.1...v8.9.2) ##### Patch Changes - Don't use reflink on Windows [#7186](https://togithub.com/pnpm/pnpm/issues/7186). - Do not run node-gyp rebuild if `preinstall` lifecycle script is present [#7206](https://togithub.com/pnpm/pnpm/pull/7206). ##### Our Gold Sponsors

##### Our Silver Sponsors

### [`v8.9.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.9.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.9.0...v8.9.1) ##### Patch Changes - Optimize selection result output of `pnpm update --interactive` [7109](https://togithub.com/pnpm/pnpm/issues/7109) - When `shared-workspace-lockfile` is set to `false`, read the pnpm settings from `package.json` files that are nested. This was broken in pnpm v8.9.0 [#7184](https://togithub.com/pnpm/pnpm/issues/7184). - Fix file cloning to `node_modules` on Windows Dev Drives [#7186](https://togithub.com/pnpm/pnpm/issues/7186). This is a fix to a regression that was shipped with v8.9.0. - `pnpm dlx` should ignore any settings that are in a `package.json` file found in the current working directory [#7198](https://togithub.com/pnpm/pnpm/issues/7198). ##### Our Gold Sponsors

##### Our Silver Sponsors

### [`v8.9.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.9.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.8.0...v8.9.0) #### Minor Changes - **🚀Performance improvement:** Use reflinks instead of hard links by default on macOS and Windows Dev Drives [#5001](https://togithub.com/pnpm/pnpm/issues/5001). - The list of packages that are allowed to run installation scripts now may be provided in a separate configuration file. The path to the file should be specified via the `pnpm.onlyBuiltDependenciesFile` field in `package.json`. For instance: ```json { "dependencies": { "@my-org/policy": "1.0.0" } "pnpm": { "onlyBuiltDependenciesFile": "node_modules/@my-org/policy/allow-build.json" } } ``` In the example above, the list is loaded from a dependency. The JSON file with the list should contain an array of package names. For instance: ```json ["esbuild", "@reflink/reflink"] ``` With the above list, only `esbuild` and `@reflink/reflink` will be allowed to run scripts during installation. Related issue: [#7137](https://togithub.com/pnpm/pnpm/issues/7137). - Add `disallow-workspace-cycles` option to error instead of warn about cyclic dependencies - Allow `env rm` to remove multiple node versions at once, and introduce `env add` for installing node versions without setting as default [#7155](https://togithub.com/pnpm/pnpm/pull/7155). #### Patch Changes - Fix memory error in `pnpm why` when the dependencies tree is too big, the command will now prune the tree to just 10 end leafs and now supports `--depth` argument [#7122](https://togithub.com/pnpm/pnpm/pull/7122). - Use `neverBuiltDependencies` and `onlyBuiltDependencies` from the root `package.json` of the workspace, when `shared-workspace-lockfile` is set to `false` [#7141](https://togithub.com/pnpm/pnpm/pull/7141). - Optimize peers resolution to avoid out-of-memory exceptions in some rare cases, when there are too many circular dependencies and peer dependencies [#7149](https://togithub.com/pnpm/pnpm/pull/7149). - Instead of `pnpm.overrides` replacing `resolutions`, the two are now merged. This is intended to make it easier to migrate from Yarn by allowing one to keep using `resolutions` for Yarn, but adding additional changes just for pnpm using `pnpm.overrides`. #### Our Gold Sponsors

#### Our Silver Sponsors

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, check this box

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

vercel[bot] commented 11 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

changeset-bot[bot] commented 11 months ago

⚠️ No Changeset found

Latest commit: cb06449e768eb125b0038eb41a7aaff2123639bc

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-commenter commented 11 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b094895) 100.00% compared to head (cb06449) 96.79%. Report is 185 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #912 +/- ## =========================================== - Coverage 100.00% 96.79% -3.21% =========================================== Files 103 67 -36 Lines 914 812 -102 Branches 160 146 -14 =========================================== - Hits 914 786 -128 - Misses 0 16 +16 - Partials 0 10 +10 ``` [see 135 files with indirect coverage changes](https://app.codecov.io/gh/morfeojs/morfeo/pull/912/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=morfeojs)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

morfeojs / morfeo