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 #86

Merged
merged 1 commit into from
Oct 12, 2023
Merged

chore(deps): update pnpm to v8 #86

merged 1 commit into from
Oct 12, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 28, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

v8.9.0

Compare Source

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

Patch Changes

  • Don't run the prepublishOnly scripts of git-hosted dependencies #​7026.
  • Fix a bug in which use-node-version or node-version isn't passed down to checkEngine when using pnpm workspace, resulting in an error #​6981.
  • Don't print out each deprecated subdependency separately with its deprecation message. Just print out a summary of all the deprecated subdependencies #​6707.
  • Fixed an ENOENT error that was sometimes happening during install with "hoisted" node_modules #​6756.

Our Gold Sponsors

Our Silver Sponsors

v8.7.5

Compare Source

Patch Changes

  • Improve performance of installation by using a worker for creating the symlinks inside node_modules/.pnpm #​7069.
  • Tarballs that have hard links are now unpacked successfully. This fixes a regression introduced in v8.7.0, which was shipped with our new in-house tarball parser #​7062.

Our Gold Sponsors

Our Silver Sponsors

v8.7.4

Compare Source

Patch Changes

  • Fix a bug causing the pnpm server to hang if a tarball worker was requested while another worker was exiting #​7041.
  • Fixes a regression published with pnpm v8.7.3. Don't hang while reading package.json from the content-addressable store #​7051.
  • Allow create scoped package with preferred version. #​7053
  • Reverting a change shipped in v8.7 that caused issues with the pnpm deploy command and "injected dependencies" #​6943.

Our Gold Sponsors

Our Silver Sponsors

v8.7.3

Compare Source

Patch Changes

  • Fix a bug causing errors to be printed as "Cannot read properties of undefined (reading 'code')" instead of the underlying reason when using the pnpm store server #​7032

Our Gold Sponsors

Our Silver Sponsors

v8.7.2

Compare Source

v8.7.1

Compare Source

Patch Changes

  • Fixed an issue with extracting some old versions of tarballs #​6991.
  • Side-effects cache will now be leveraged when running install in a workspace that uses dedicated lockfiles for each project #​6890.
  • Reduce concurrency in the pnpm -r publish command #​6968.
  • Improved the pnpm update --interactive output by grouping dependencies by type. Additionally, a new column has been added with links to the documentation for outdated packages #​6978.

Our Gold Sponsors

Our Silver Sponsors

v8.7.0

Compare Source

Minor Changes

  • Improve performance of installation by using a worker pool for extracting packages and writing them to the content-addressable store #​6850
  • The default value of the resolution-mode setting is changed to highest. This setting was changed to lowest-direct in v8.0.0 and some users were not happy with the change. A twitter poll concluded that most of the users want the old behaviour (resolution-mode set to highest by default). This is a semi-breaking change but should not affect users that commit their lockfile #​6463.

Patch Changes

  • Warn when linking a package with peerDependencies #​615.
  • Add support for npm lockfile v3 in pnpm import #​6233.
  • Override peerDependencies in pnpm.overrides #​6759.
  • Respect workspace alias syntax in pkg graph #​6922
  • Emit a clear error message when users attempt to specify an undownloadable node version #​6916.
  • pnpm patch should write patch files with a trailing newline #​6905.
  • Dedupe deps with the same alias in direct dependencies 6966
  • Don't prefix install output for the dlx command.
  • Performance optimizations. Package tarballs are now download directly to memory and built to an ArrayBuffer. Hashing and other operations are avoided until the stream has been fully received #​6819.

Our Gold Sponsors

Our Silver Sponsors

v8.6.12

Compare Source

Patch Changes

  • Make the error message friendlier when a user attempts to run a command that does not exist #​6887.
  • pnpm patch should work correctly when shared-workspace-file is set to false #​6885.
  • pnpm env use should retry deleting the previous Node.js executable #​6587.
  • pnpm dlx should not print an error stack when the underlying script execution fails #​6698.
  • When showing the download progress of large tarball files, always display the same number of digits after the decimal point #​6901.
  • Report download progress less frequently to improve performance #​6906.
  • pnpm install --frozen-lockfile --lockfile-only should fail if the lockfile is not up to date with the package.json files #​6913.

Our Gold Sponsors

Our Silver Sponsors

v8.6.11

Compare Source

Patch Changes

  • Change the install error message when a lockfile is wanted but absent to indicate the wanted lockfile is absent, not present. This now reflects the actual error #​6851.
  • When dealing with a local dependency that is a path to a symlink, a new symlink should be created to the original symlink, not to the actual directory location.
  • The length of the temporary file names in the content-addressable store reduced in order to prevent ENAMETOOLONG errors from happening #​6842.
  • Don't print "added" stats, when installing with --lockfile-only.
  • Installation of a git-hosted dependency should not fail if the pnpm-lock.yaml file of the installed dependency is not up-to-date #​6865.
  • Don't ignore empty strings in params #​6594.
  • Always set dedupe-peer-dependents to false, when running installation during deploy #​6858.
  • When several containers use the same store simultaneously, there's a chance that multiple containers may create a temporary file at the same time. In such scenarios, pnpm could fail to rename the temporary file in one of the containers. This issue has been addressed: pnpm will no longer fail if the temporary file is absent but the destination file exists.
  • Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) #​6863.

Our Gold Sponsors

Our Silver Sponsors

v8.6.10

Compare Source

Patch Changes
  • Installation succeeds if a non-optional dependency of an optional dependency has failing installation scripts #​6822.
  • The length of the temporary file names in the content-addressable store reduced in order to prevent ENAMETOOLONG errors from happening #​6842.
  • Ignore empty patch content when patch-commit.
  • Sort keys in packageExtensions before calculating packageExtensionsChecksum #​6824.
  • Pass the right scheme to git ls-remote in order to prevent a fallback to git+ssh that would result in a 'host key verification failed' issue #​6806
  • The "postpublish" script of a git-hosted dependency is not executed, while building the dependency #​6822.
Our Gold Sponsors
Our Silver Sponsors

v8.6.9

Compare Source

Patch Changes

  • Temporarily revert the fix to #​6805 to fix the regression it caused #​6827.

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.


  • 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 30, 2023

Codecov Report

Merging #86 (fd8976c) into main (d089293) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #86   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           82        82           
  Branches        25        25           
=========================================
  Hits            82        82           

@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from feb3396 to e05a4fd Compare April 10, 2023 01:19
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from ae0d7be to 15995ff Compare April 19, 2023 17:06
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 6652990 to df86457 Compare April 29, 2023 01:27
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 8fc2ac9 to c67e189 Compare May 15, 2023 04:46
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 338808a to a286c97 Compare June 5, 2023 15:13
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from 1938af6 to 6d65528 Compare June 26, 2023 12:21
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 82bb24a to 6e5d79d Compare July 10, 2023 00:20
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from 71e0a40 to 7aa056f Compare July 24, 2023 01:02
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 7e695e8 to 7dfcfc1 Compare August 6, 2023 12:01
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 3c87089 to f2257af Compare August 31, 2023 17:30
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 757c3fd to 3625193 Compare September 11, 2023 16:48
@danielroe danielroe merged commit bbc3c70 into main Oct 12, 2023
3 checks passed
@renovate renovate bot deleted the renovate/pnpm-8.x branch October 12, 2023 12:42
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.

None yet

1 participant