Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update pnpm to v8.12.1 #59

Merged
merged 1 commit into from
Dec 13, 2023
Merged

chore(deps): update pnpm to v8.12.1 #59

merged 1 commit into from
Dec 13, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 12, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

v8.12.1

Compare Source

Patch Changes

  • Don't report dependencies with optional dependencies as being added on repeat install. This was a bug in reporting #​7384.
  • Fix a bug where --fix-lockfile crashes on tarballs #​7368.
  • Do not create empty patch directory.
  • Installation should not fail if an empty node_modules directory cannot be removed #​7405.

Our Gold Sponsors

Our Silver Sponsors

v8.12.0

Compare Source

Minor Changes

  • Add support for basic authorization header #​7371.

Patch Changes

  • Fix a bug where pnpm incorrectly passes a flag to a run handler as a fallback command #​7244.
  • When dedupe-direct-deps is set to true, commands of dependencies should be deduplicated #​7359.

Our Gold Sponsors

Our Silver Sponsors

v8.11.0

Compare Source

Minor Changes

  • (IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain /<pkg_name>@&#8203;<pkg_version, not <domain>/<pkg_name>@&#8203;<pkg_version>.

    This change is a fix to avoid the same package from being added to node_modules/.pnpm multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.

    We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.

    Related PR: #​7318.

Patch Changes

  • pnpm add a-module-already-in-dev-deps will show a message to notice the user that the package was not moved to "dependencies" #​926.
  • The modules directory should not be removed if the registry configuration has changed.
  • Fix missing auth tokens in registries with paths specified (e.g. //npm.pkg.github.com/pnpm). #​5970 #​2933

Our Gold Sponsors

Our Silver Sponsors

v8.10.5

Compare Source

Patch Changes

  • Don't fail on an empty pnpm-workspace.yaml file #​7307.

Our Gold Sponsors

Our Silver Sponsors

v8.10.4

Compare Source

Patch Changes

  • Fixed out-of-memory exception that was happening on dependencies with many peer dependencies, when node-linker was set to hoisted #​6227.

Our Gold Sponsors

Our Silver Sponsors

v8.10.3

Compare Source

Patch Changes

  • (Important) Increased the default amount of allowed concurrent network request on systems that have more than 16 CPUs #​7285.

  • pnpm patch should reuse existing patch when shared-workspace-file=false #​7252.

  • Don't retry fetching missing packages, since the retries will never work #​7276.

  • When using pnpm store prune --force alien directories are removed from the store #​7272.

  • Downgraded npm-packlist because the newer version significantly slows down the installation of local directory dependencies, making it unbearably slow.

    npm-packlist was upgraded in this PR to fix #​6997. We added our own file deduplication to fix the issue of duplicate file entries.

  • Fixed a performance regression on running installation on a project with an up to date lockfile #​7297.

  • Throw an error on invalid pnpm-workspace.yaml file #​7273.

Our Gold Sponsors

Our Silver Sponsors


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 5am every weekday,before 8pm every weekday" (UTC).

🚦 Automerge: Enabled.

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.

@renovate renovate bot changed the title chore(deps): update pnpm to v8.10.3 chore(deps): update pnpm to v8.10.4 Nov 13, 2023
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 235123a to d083f80 Compare November 13, 2023 17:38
@renovate renovate bot changed the title chore(deps): update pnpm to v8.10.4 chore(deps): update pnpm to v8.10.5 Nov 14, 2023
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from d083f80 to 71928c3 Compare November 14, 2023 14:24
@renovate renovate bot changed the title chore(deps): update pnpm to v8.10.5 chore(deps): update pnpm to v8.11.0 Nov 24, 2023
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 71928c3 to bb29806 Compare November 24, 2023 19:15
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 6 times, most recently from 3c0d6dd to 47ba5b9 Compare December 9, 2023 01:37
@renovate renovate bot changed the title chore(deps): update pnpm to v8.11.0 chore(deps): update pnpm to v8.12.0 Dec 9, 2023
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 47ba5b9 to 26a6b95 Compare December 13, 2023 10:57
@renovate renovate bot changed the title chore(deps): update pnpm to v8.12.0 chore(deps): update pnpm to v8.12.1 Dec 13, 2023
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from 2580ae6 to 325a1be Compare December 13, 2023 14:55
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 325a1be to 4a25731 Compare December 13, 2023 15:39
@renovate renovate bot merged commit 2cf08cf into main Dec 13, 2023
@renovate renovate bot deleted the renovate/pnpm-8.x branch December 13, 2023 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants