stable-packages / store

provides version stable stores for library.
MIT License
6 stars 0 forks source link

chore(deps): update pnpm to v8.1.0 #191

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) 8.0.0 -> 8.1.0 age adoption passing confidence

Release Notes

pnpm/pnpm ### [`v8.1.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.1.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.0.0...v8.1.0) ##### Minor Changes - A new setting has been added called `dedupe-direct-deps`, which is disabled by default. When set to `true`, dependencies that are already symlinked to the root `node_modules` directory of the workspace will not be symlinked to subproject `node_modules` directories. This feature was enabled by default in v8.0.0 but caused issues, so it's best to disable it by default [#​6299](https://togithub.com/pnpm/pnpm/issues/6299). - Add `ignore-workspace-cycles` to silence workspace cycle warning [#​6308](https://togithub.com/pnpm/pnpm/pull/6308). ##### Patch Changes - Print the right lowest supported Node.js version in the error message, when pnpm is executed with an old Node.js version [#​6297](https://togithub.com/pnpm/pnpm/issues/6297). - Improve the outdated lockfile error message [#​6304](https://togithub.com/pnpm/pnpm/pull/6304). ##### 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.



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

changeset-bot[bot] commented 1 year ago

⚠️ No Changeset found

Latest commit: a2039baa5041e0ae718094e52e53f2e9684a70b1

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] commented 1 year ago

Codecov Report

Patch and project coverage have no change.

Comparison is base (3f2ded8) 100.00% compared to head (a2039ba) 100.00%.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #191 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 7 7 Lines 86 86 Branches 20 20 ========================================= Hits 86 86 ``` Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Homa+Wong). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Homa+Wong)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.