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 - autoclosed #45

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 28, 2023

Mend Renovate logo banner

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

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

v8.10.2

Compare Source

Patch Changes

  • Fixed a regression that was shipped with pnpm v8.10.0. Dependencies that were already built should not be rebuilt on repeat install. This issue was introduced via the changes related to supportedArchitectures. Related issue #​7268.

Our Gold Sponsors

Our Silver Sponsors

v8.10.1

Compare Source

Patch Changes

  • (Important) Tarball resolutions in pnpm-lock.yaml will no longer contain a registry field. This field has been unused for a long time. This change should not cause any issues besides backward compatible modifications to the lockfile #​7262.
  • Fix issue when trying to use pnpm dlx in the root of a Windows Drive #​7263.
  • Optional dependencies that do not have to be built will be reflinked (or hardlinked) to the store instead of copied #​7046.
  • If a package's tarball cannot be fetched, print the dependency chain that leads to the failed package #​7265.
  • After upgrading one of our dependencies, we started to sometimes have an error on publish. We have forked @npmcli/arborist to patch it with a fix #​7269.

Our Gold Sponsors

Our Silver Sponsors

v8.10.0

Compare Source

Minor Changes
  • Support for multiple architectures when installing dependencies #​5965.

    You can now specify architectures for which you'd like to install optional dependencies, even if they don't match the architecture of the system running the install. Use the supportedArchitectures field in package.json to define your preferences.

    For example, the following configuration tells pnpm to install optional dependencies for Windows x64:

    {
      "pnpm": {
        "supportedArchitectures": {
          "os": ["win32"],
          "cpu": ["x64"]
        }
      }
    }

    Whereas this configuration will have pnpm install optional dependencies for Windows, macOS, and the architecture of the system currently running the install. It includes artifacts for both x64 and arm64 CPUs:

    {
      "pnpm": {
        "supportedArchitectures": {
          "os": ["win32", "darwin", "current"],
          "cpu": ["x64", "arm64"]
        }
      }
    }

    Additionally, supportedArchitectures also supports specifying the libc of the system.

  • The pnpm licenses list command now accepts the --filter option to check the licenses of the dependencies of a subset of workspace projects #​5806.

Patch Changes
  • Allow scoped name as bin name #​7112.

  • When running scripts recursively inside a workspace, the logs of the scripts are grouped together in some CI tools. (Only works with --workspace-concurrency 1)

  • Print a warning when installing a dependency from a non-existent directory #​7159

  • Should fetch dependency from tarball url when patching dependency installed from git #​7196

  • pnpm setup should add a newline at the end of the updated shell config file #​7227.

  • Improved the performance of linking bins of hoisted dependencies to node_modules/.pnpm/node_modules/.bin #​7212.

  • Wrongful ELIFECYCLE error on program termination #​7164.

  • pnpm publish should not pack the same file twice sometimes #​6997.

    The fix was to update npm-packlist to the latest version.

Our Gold Sponsors
Our Silver Sponsors

v8.9.2

Compare Source

Patch Changes
  • Don't use reflink on Windows #​7186.
  • Do not run node-gyp rebuild if preinstall lifecycle script is present #​7206.
Our Gold Sponsors
Our Silver Sponsors

v8.9.1

Compare Source

Patch Changes
  • Optimize selection result output of pnpm update --interactive 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.
  • Fix file cloning to node_modules on Windows Dev Drives #​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.
Our Gold Sponsors
Our Silver Sponsors

v8.9.0

Compare Source

Minor Changes

  • 🚀Performance improvement: Use reflinks instead of hard links by default on macOS and Windows Dev Drives #​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:

    {
      "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:

    ["esbuild", "@​reflink/reflink"]

    With the above list, only esbuild and @reflink/reflink will be allowed to run scripts during installation.

    Related issue: #​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.

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.
  • Use neverBuiltDependencies and onlyBuiltDependencies from the root package.json of the workspace, when shared-workspace-lockfile is set to false #​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.
  • 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

v8.8.0

Compare Source

Minor Changes

  • Add --reporter-hide-prefix option for run command to hide project name as prefix for lifecycle log outputs of running scripts #​7061.

Patch Changes

  • Pass through the --ignore-scripts command to install, when running pnpm dedupe --ignore-scripts #​7102.
  • Throw meaningful error for config sub commands#​7106.
  • When the node-linker is set to hoisted, the package.json files of the existing dependencies inside node_modules will be checked to verify their actual versions. The data in the node_modules/.modules.yaml and node_modules/.pnpm/lock.yaml may not be fully reliable, as an installation may fail after changes to dependencies were made but before those state files were updated #​7107.
  • Don't update git-hosted dependencies when adding an unrelated dependency #​7008.

Our Gold Sponsors

Our Silver Sponsors

v8.7.6

Compare Source


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.

@codecov
Copy link

codecov bot commented Mar 28, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (21f19ba) 100.00% compared to head (192f487) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #45   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines          131       131           
  Branches        35        35           
=========================================
  Hits           131       131           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 7f64754 to 1719256 Compare April 4, 2023 06:29
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 1719256 to b10a4ce Compare April 10, 2023 01:43
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from c8def2f to e777f2d Compare April 23, 2023 01:41
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from e777f2d to 2235f4c Compare May 2, 2023 13:56
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 9b262fe to 7300850 Compare May 15, 2023 02:05
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from e4d624e to 0ab4772 Compare June 5, 2023 14:51
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 0ab4772 to 9753e3f Compare June 11, 2023 21:54
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from 6f7853c to 7ce2523 Compare June 26, 2023 13:34
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from c4dbc58 to af22879 Compare July 10, 2023 01:27
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from 9d1e929 to 3268269 Compare July 24, 2023 00:45
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 2a40dc1 to b3c6b5a Compare August 6, 2023 12:14
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from ae5a231 to e1974e9 Compare August 31, 2023 19:19
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 4 times, most recently from 53f2b6f to 37c1283 Compare September 11, 2023 14:39
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 37c1283 to 0dbc6c5 Compare September 17, 2023 20:26
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 0dbc6c5 to ace2ea0 Compare September 26, 2023 16:03
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from 6825527 to 81c3fad Compare October 16, 2023 00:11
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from 1addec3 to ec88607 Compare November 1, 2023 19:43
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from d93a629 to 27d5572 Compare November 13, 2023 18:07
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch from 27d5572 to 192f487 Compare November 14, 2023 14:19
@renovate renovate bot changed the title chore(deps): update pnpm to v8 chore(deps): update pnpm to v8 - autoclosed Nov 15, 2023
@renovate renovate bot closed this Nov 15, 2023
@renovate renovate bot deleted the renovate/pnpm-8.x branch November 15, 2023 16:49
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