i7eo / unconfig

🚀 A modern, high-performance monorepo project built to simplify project config!
https://unconfig.i7eo.com
MIT License
4 stars 2 forks source link

chore(deps): update pnpm to v8 - autoclosed #14

Closed renovate[bot] closed 2 months ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pnpm (source) >=7 -> >=8.6.6 age adoption passing confidence
pnpm (source) 7.25.0 -> 8.6.6 age adoption passing confidence

Release Notes

pnpm/pnpm (pnpm) ### [`v8.6.6`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.6) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.5...v8.6.6) #### Patch Changes - Installation of a git-hosted dependency without `package.json` should not fail, when the dependency is read from cache [#​6721](https://togithub.com/pnpm/pnpm/issues/6721). - Local workspace bin files that should be compiled first are linked to dependent projects after compilation [#​1801](https://togithub.com/pnpm/pnpm/issues/1801). - Prefer versions found in parent package dependencies only [#​6737](https://togithub.com/pnpm/pnpm/issues/6737). - Multiple performance optimizations implemented by [@​zxbodya](https://togithub.com/zxbodya): - avoid copying `preferredVersions` object [#​6735](https://togithub.com/pnpm/pnpm/issues/6735) - avoid object copy in `resolvePeersOfNode` [#​6736](https://togithub.com/pnpm/pnpm/issues/6736) - `preferredVersions` in `resolveDependenciesOfImporters` [#​6748](https://togithub.com/pnpm/pnpm/issues/6748) - remove ramda `isEmpty` usages [#​6753](https://togithub.com/pnpm/pnpm/issues/6753) - use Maps and Sets instead of objects [#​6749](https://togithub.com/pnpm/pnpm/issues/6749) - optimize `splitNodeId`, fix invalid `nodeId` [#​6755](https://togithub.com/pnpm/pnpm/issues/6755) #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.6.5`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.5) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.4...v8.6.5) #### Patch Changes - Improve the performance of searching for auth tokens [#​6717](https://togithub.com/pnpm/pnpm/pull/6717). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.6.4`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.4) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.3...v8.6.4) #### Patch Changes - In cases where both aliased and non-aliased dependencies exist to the same package, non-aliased dependencies will be used for resolving peer dependencies, addressing issue [#​6588](https://togithub.com/pnpm/pnpm/issues/6588). - Ignore the port in the URL, while searching for authentication token in the `.npmrc` file [#​6354](https://togithub.com/pnpm/pnpm/issues/6354). - Don't add the version of a local directory dependency to the lockfile. This information is not used anywhere by pnpm and is only causing more Git conflicts [#​6695](https://togithub.com/pnpm/pnpm/pull/6695). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.6.3`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.2...v8.6.3) #### Patch Changes - When running a script in multiple projects, the script outputs should preserve colours [#​2148](https://togithub.com/pnpm/pnpm/issues/2148). - Don't crash when the `APPDATA` env variable is not set on Windows [#​6659](https://togithub.com/pnpm/pnpm/issues/6659). - Don't fail when a package is archived in a tarball with malformed tar headers [#​5362](https://togithub.com/pnpm/pnpm/issues/5362). - Peer dependencies of subdependencies should be installed, when `node-linker` is set to `hoisted` [#​6680](https://togithub.com/pnpm/pnpm/pull/6680). - Throw a meaningful error when applying a patch to a dependency fails. - `pnpm update --global --latest` should work [#​3779](https://togithub.com/pnpm/pnpm/issues/3779). - `pnpm license ls` should work even when there is a patched git protocol dependency [#​6595](https://togithub.com/pnpm/pnpm/issues/6595) #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.6.2`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.1...v8.6.2) #### Patch Changes - Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly [#​6648](https://togithub.com/pnpm/pnpm/issues/6648) - When patching a dependency, only consider files specified in the 'files' field of its package.json. Ignore all others [#​6565](https://togithub.com/pnpm/pnpm/issues/6565) - Should always treat local file dependency as new dependency [#​5381](https://togithub.com/pnpm/pnpm/issues/5381) - Output a warning message when "pnpm" or "resolutions" are configured in a non-root workspace project [#​6636](https://togithub.com/pnpm/pnpm/issues/6636) #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.6.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.0...v8.6.1) #### Patch Changes - When `dedupe-peer-dependents` is enabled (default), use the path (not id) to determine compatibility. When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication. Resolves: [#​6605](https://togithub.com/pnpm/pnpm/issues/6605) - Some minor performance improvements by removing await from loops [#​6617](https://togithub.com/pnpm/pnpm/pull/6617). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.6.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.5.1...v8.6.0) ##### Minor Changes - Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created. A new field will now be present in the lockfile: `settings`. It will store the values of two settings: `autoInstallPeers` and `excludeLinksFromLockfile`. If someone tries to perform a `frozen-lockfile` installation and their active settings don't match the ones in the lockfile, then an error message will be thrown. The lockfile format version is bumped from v6.0 to v6.1. Related PR: [#​6557](https://togithub.com/pnpm/pnpm/pull/6557) Related issue: [#​6312](https://togithub.com/pnpm/pnpm/issues/6312) - A new setting, `exclude-links-from-lockfile`, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile. This setting was primarily added for use by [Bit CLI](https://togithub.com/teambit/bit), which links core aspects to `node_modules` from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations. ##### Patch Changes - Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks [#​6544](https://togithub.com/pnpm/pnpm/issues/6544). - When updating dependencies, preserve the range prefix in aliased dependencies. So `npm:foo@1.0.0` becomes `npm:foo@1.1.0`. - Print a meaningful error when a project referenced by the `workspace:` protocol is not found in the workspace [#​4477](https://togithub.com/pnpm/pnpm/issues/4477). - `pnpm rebuild` should not fail when `node-linker` is set to `hoisted` and there are skipped optional dependencies [#​6553](https://togithub.com/pnpm/pnpm/pull/6553). - Peers resolution should not fail when a linked in dependency resolves a peer dependency. - Build projects in a workspace in correct order [#​6568](https://togithub.com/pnpm/pnpm/pull/6568). ##### Our Gold Sponsors
##### Our Silver Sponsors
### [`v8.5.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.5.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.5.0...v8.5.1) #### Patch Changes - Expanded missing command error, including 'did you mean' [#​6492](https://togithub.com/pnpm/pnpm/issues/6492). - When installation fails because the lockfile is not up-to-date with the `package.json` file(s), print out what are the differences [#​6536](https://togithub.com/pnpm/pnpm/pull/6536). - Normalize current working directory on Windows [#​6524](https://togithub.com/pnpm/pnpm/issues/6524). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.5.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.5.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.4.0...v8.5.0) #### Minor Changes - `pnpm patch-remove` command added [#​6521](https://togithub.com/pnpm/pnpm/pull/6521). #### Patch Changes - `pnpm link -g ` should not modify the `package.json` file [#​4341](https://togithub.com/pnpm/pnpm/issues/4341). - The deploy command should not ask for confirmation to purge the `node_modules` directory [#​6510](https://togithub.com/pnpm/pnpm/issues/6510). - Show cyclic workspace dependency details [#​5059](https://togithub.com/pnpm/pnpm/issues/5059). - Node.js range specified through the `engines` field should match prerelease versions [#​6509](https://togithub.com/pnpm/pnpm/pull/6509). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.4.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.4.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.3.1...v8.4.0) ##### Minor Changes - `pnpm publish` supports the `--provenance` CLI option [#​6435](https://togithub.com/pnpm/pnpm/issues/6435). ##### Patch Changes - Link the bin files of local workspace dependencies, when `node-linker` is set to `hoisted` [6486](https://togithub.com/pnpm/pnpm/issues/6486). - Ask the user to confirm the removal of `node_modules` directory unless the `--force` option is passed. - Do not create a `node_modules` folder with a `.modules.yaml` file if there are no dependencies inside `node_modules`. ##### Our Gold Sponsors
##### Our Silver Sponsors
### [`v8.3.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.3.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.3.0...v8.3.1) ##### Patch Changes - Patch `node-fetch` to fix an error that happens on Node.js 20 [#​6424](https://togithub.com/pnpm/pnpm/issues/6424). ##### Our Gold Sponsors
##### Our Silver Sponsors
### [`v8.3.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.3.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.2.0...v8.3.0) ##### Minor Changes - A custom compression level may be specified for the `pnpm pack` command using the `pack-gzip-level` setting [#​6393](https://togithub.com/pnpm/pnpm/issues/6393). - Add `--check` flag to `pnpm dedupe`. No changes will be made to `node_modules` or the lockfile. Exits with a non-zero status code if changes are possible. - `pnpm install --resolution-only` re-runs resolution to print out any peer dependency issues [#​6411](https://togithub.com/pnpm/pnpm/pull/6411). ##### Patch Changes - Warn user when `publishConfig.directory` of an injected workspace dependency does not exist [#​6396](https://togithub.com/pnpm/pnpm/pull/6396). - Use hard links to link the node executable on Windows machines [#​4315](https://togithub.com/pnpm/pnpm/issues/4315). ##### Our Gold Sponsors

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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 these updates 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.

changeset-bot[bot] commented 1 year ago

⚠️ No Changeset found

Latest commit: 0010ff7f635cfeece0285648d94989aae6a270b7

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

i7eo commented 1 year ago

Marking pull request as stale since there was no activity for 30 days