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 v7 #53

Merged
merged 1 commit into from
Feb 3, 2023
Merged

chore(deps): update pnpm to v7 #53

merged 1 commit into from
Feb 3, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 2, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm

v7.26.3

Compare Source

Patch Changes

  • Directories inside the virtual store should not contain the ( or ) chars. This is to fix issues with storybook and the new v6 pnpm-lock.yaml lockfile format #​5976.
  • The update command should not replace dependency versions specified via dist-tags #​5996.
  • Fixed an issue that was causing pnpm to stuck forever during installation #​5909.

Our Gold Sponsors

Our Silver Sponsors

v7.26.2

Compare Source

Patch Changes

  • Wrap text in pnpm audit output for better readability #​5981
  • Fix "cross-device link not permitted" error when node-linker is set to hoisted #​5992.

Our Gold Sponsors

Our Silver Sponsors

v7.26.1

Compare Source

Patch Changes

  • Fixed out of memory error that sometimes happens when node-linker is set to hoisted #​5988.
  • Fixed EMFILE: too many open files by using graceful-fs for reading bin files of dependencies #​5887.
  • Fix lockfile v6 on projects that use patched dependencies #​5967.

Our Gold Sponsors

Our Silver Sponsors

v7.26.0

Compare Source

Minor Changes

Patch Changes

  • Packages hoisted to the virtual store are not removed on repeat install, when the non-headless algorithm runs the installation #​5971.
  • prepublishOnly and prepublish should not be executed on pnpm pack #​2941.

Our Gold Sponsors

Our Silver Sponsors

v7.25.1

Compare Source

Patch Changes

  • Show dependency paths info in pnpm audit output #​3073
  • The store integrity check should validate the side effects cache of the installed package. If the side effects cache is broken, the package needs to be rebuilt #​4997.
  • Add more info to the description of the --force option in the pnpm install command #​5932.
  • Don't crash when a bin file is not found and prefer-symlinked-executables is true #​5946.
  • pnpm install --fix-lockfile should not fail if the package has no dependencies #​5878.

Our Gold Sponsors

Our Silver Sponsors

v7.25.0

Compare Source

Minor Changes

  • When patching a dependency that is already patched, the existing patch is applied to the dependency, so that the new edit are applied on top of the existing ones. To ignore the existing patches, run the patch command with the --ignore-existing option #​5632.
  • When extend-node-path is set to false, the NODE_PATH environment variable is not set in the command shims #​5910

Patch Changes

  • Ensure the permission of bin file when prefer-symlinked-executables is set to true #​5913.
  • If an external tool or a user have removed a package from node_modules, pnpm should add it back on install. This was only an issue with node-linker=hoisted.

Our Gold Sponsors

Our Silver Sponsors

v7.24.3

Compare Source

Patch Changes

  • Don't break lockfile v6 on repeat install if use-lockfile-v6 is not set to true.

Our Gold Sponsors

Our Silver Sponsors

v7.24.2

Compare Source

Minor Changes

  • Added support for pnpm-lock.yaml format v6. This new format will be the new lockfile format in pnpm v8. To use the new lockfile format, use the use-lockfile-v6=true setting in .npmrc. Or run pnpm install --use-lockfile-v6 #​5810.

Patch Changes

  • pnpm run should fail if the path to the project contains colon(s).

  • pnpm config set key=value should work the same as pnpm config set key value #​5889.

  • The upload of built artifacts (side effects) should not fail when node-linker is set to hoisted and installation runs on a project that already had a node_modules directory #​5823.

    This fixes a bug introduced by #​5814.

  • pnpm exec should work when the path to the project contains colon(s) #​5846.

  • Git-hosted dependencies should not be built, when ignore-scripts is set to true #​5876.

Our Gold Sponsors

Our Silver Sponsors

v7.24.1

Compare Source

v7.24.0

Compare Source

v7.23.0

Compare Source

Minor Changes

  • When the resolve-peers-from-workspace-root setting is set to true, pnpm will use dependencies installed in the root of the workspace to resolve peer dependencies in any of the workspace's projects #​5882.

Patch Changes

  • The help of the run command should list the --resume-from option.
  • Should display --include-workspace-root option on recursive command's help info.

Our Gold Sponsors

Our Silver Sponsors

v7.22.0

Compare Source

Minor Changes

  • The pnpm list and pnpm why commands will now look through transitive dependencies of workspace: packages. A new --only-projects flag is available to only print workspace: packages.
  • pnpm exec and pnpm run command support --resume-from option. When used, the command will executed from given package #​4690.
  • Expose the npm_command environment variable to lifecycle hooks & scripts.

Patch Changes

  • Fix a situation where pnpm list and pnpm why may not respect the --depth argument.
  • Report to the console when a git-hosted dependency is built #​5847.
  • Throw an accurate error message when trying to install a package that has no versions, or all of its versions are unpublished #​5849.
  • replace dependency is-ci by ci-info (is-ci is just a simple wrapper around ci-info).
  • Only run prepublish scripts of git-hosted dependencies, if the dependency doesn't have a main file. In this case we can assume that the dependencies has to be built.
  • Print more contextual information when a git-hosted package fails to be prepared for installation #​5847.

Our Gold Sponsors

Our Silver Sponsors

v7.21.0

Compare Source

Minor Changes

  • The pnpm dlx command supports the --shell-mode (or -c) option. When used, the script is executed by a shell #​5679.

Patch Changes

  • The config command should work with the --location=global CLI option #​5841.
  • Only the pnpm add --global <pkg> command should fail if there is no global pnpm bin directory in the system PATH #​5841.

Our Gold Sponsors

Our Silver Sponsors

v7.20.0

Compare Source

Minor Changes

  • pnpm gets its own implementation of the following commands:

    • pnpm config get
    • pnpm config set
    • pnpm config delete
    • pnpm config list

    In previous versions these commands were passing through to npm CLI.

    PR: #​5829
    Related issue: #​5621

  • Add show alias to pnpm view #​5835.

  • pnpm reads settings from its own global configuration file at $XDG_CONFIG_HOME/pnpm/rc #​5829.

  • Add the 'description'-field to the licenses output #​5836.

Patch Changes

  • pnpm rebuild should not fail if node_modules was created by pnpm version 7.18 or older #​5815.
  • pnpm env should print help.
  • Run the prepublish scripts of packages installed from Git #​5826.
  • pnpm rebuild should print a better error message when a hoisted dependency is not found #​5815.

Our Gold Sponsors

Our Silver Sponsors

v7.19.0

Compare Source

Minor Changes

  • New setting supported in the package.json that is in the root of the workspace: pnpm.requiredScripts. Scripts listed in this array will be required in each project of the worksapce. Otherwise, pnpm -r run <script name> will fail #​5569.
  • When the hoisted node linker is used, preserve node_modules directories when linking new dependencies. This improves performance, when installing in a project that already has a node_modules directory #​5795.
  • When the hoisted node linker is used, pnpm should not build the same package multiple times during installation. If a package is present at multipe locations because hoisting could not hoist them to a single directory, then the package should only built in one of the locations and copied to the rest #​5814.

Patch Changes

  • pnpm rebuild should work in projects that use the hoisted node linker #​5560.
  • pnpm patch should print instructions about how to commit the changes #​5809.
  • Allow the -S flag in command shims pnpm/cmd-shim#​42.
  • Don't relink injected directories if they were not built #​5792.

Our Gold 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.

@2nthony 2nthony merged commit 7547c32 into main Feb 3, 2023
@delete-merged-branch delete-merged-branch bot deleted the renovate/pnpm-7.x branch February 3, 2023 02:05
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.

1 participant