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

Closed
wants to merge 1 commit into from

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.33.4 -> 8.6.8 age adoption passing confidence

Release Notes

pnpm/pnpm (pnpm)

v8.6.8

Compare Source

Patch Changes

  • When the same file is appended multiple times into a tarball, the last occurrence is selected when unpacking the tarball.
  • Fixed a bug in which pnpm passed the wrong scheme to git ls-remote, causing a fallback to git+ssh and resulting in a 'host key verification failed' issue #​6805.
  • Added support for publishConfig.registry in package.json for publishing #​6775.
  • pnpm rebuild now uploads the built artifacts to the content-addressable store.
  • If a command cannot be created in .bin, the exact error message is now displayed.
  • Treat linked dependencies with a tag version type as up-to-date #​6592.
  • pnpm setup now prints more details when it cannot detect the active shell.

Our Gold Sponsors

Our Silver Sponsors

v8.6.7

Compare Source

Patch Changes

  • Ensure consistent output for scripts executed concurrently, both within a single project and across multiple projects. Each script's output will now be printed in a separate section of the terminal, when running multiple scripts in a single project using regex #​6692.
  • The --parallel CLI flag should work on single project #​6692.
  • Optimizing project manifest normalization, reducing amoung of data copying #​6763.
  • Move loading wantedLockfile outside dependenciesHierarchyForPackage, preventing OOM crash when loading the same lock file too many times #​6757.
  • Replace ineffective use of ramda difference with better alternative #​6760.

Our Gold Sponsors

Our Silver Sponsors

v8.6.6

Compare Source

Patch Changes

  • Installation of a git-hosted dependency without package.json should not fail, when the dependency is read from cache #​6721.
  • Local workspace bin files that should be compiled first are linked to dependent projects after compilation #​1801.
  • Prefer versions found in parent package dependencies only #​6737.
  • Multiple performance optimizations implemented by @​zxbodya:
    • avoid copying preferredVersions object #​6735
    • avoid object copy in resolvePeersOfNode #​6736
    • preferredVersions in resolveDependenciesOfImporters #​6748
    • remove ramda isEmpty usages #​6753
    • use Maps and Sets instead of objects #​6749
    • optimize splitNodeId, fix invalid nodeId #​6755

Our Gold Sponsors

Our Silver Sponsors

v8.6.5

Compare Source

Patch Changes

  • Improve the performance of searching for auth tokens #​6717.

Our Gold Sponsors

Our Silver Sponsors

v8.6.4

Compare Source

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.
  • Ignore the port in the URL, while searching for authentication token in the .npmrc file #​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.

Our Gold Sponsors

Our Silver Sponsors

v8.6.3

Compare Source

Patch Changes

  • When running a script in multiple projects, the script outputs should preserve colours #​2148.
  • Don't crash when the APPDATA env variable is not set on Windows #​6659.
  • Don't fail when a package is archived in a tarball with malformed tar headers #​5362.
  • Peer dependencies of subdependencies should be installed, when node-linker is set to hoisted #​6680.
  • Throw a meaningful error when applying a patch to a dependency fails.
  • pnpm update --global --latest should work #​3779.
  • pnpm license ls should work even when there is a patched git protocol dependency #​6595

Our Gold Sponsors

Our Silver Sponsors

v8.6.2

Compare Source

Patch Changes

  • Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly #​6648
  • When patching a dependency, only consider files specified in the 'files' field of its package.json. Ignore all others #​6565
  • Should always treat local file dependency as new dependency #​5381
  • Output a warning message when "pnpm" or "resolutions" are configured in a non-root workspace project #​6636

Our Gold Sponsors

Our Silver Sponsors

v8.6.1

Compare Source

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

  • Some minor performance improvements by removing await from loops #​6617.

Our Gold Sponsors

Our Silver Sponsors

v8.6.0

Compare Source

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
    Related issue: #​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, 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.
  • 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.
  • pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
  • Peers resolution should not fail when a linked in dependency resolves a peer dependency.
  • Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v8.5.1

Compare Source

Patch Changes

  • Expanded missing command error, including 'did you mean' #​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.
  • Normalize current working directory on Windows #​6524.

Our Gold Sponsors

Our Silver Sponsors

v8.5.0

Compare Source

Minor Changes

  • pnpm patch-remove command added #​6521.

Patch Changes

  • pnpm link -g <pkg-name> should not modify the package.json file #​4341.
  • The deploy command should not ask for confirmation to purge the node_modules directory #​6510.
  • Show cyclic workspace dependency details #​5059.
  • Node.js range specified through the engines field should match prerelease versions #​6509.

Our Gold Sponsors

Our Silver Sponsors

v8.4.0

Compare Source

Minor Changes

  • pnpm publish supports the --provenance CLI option #​6435.

Patch Changes

  • Link the bin files of local workspace dependencies, when node-linker is set to hoisted 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

Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Mar 28, 2023

Codecov Report

Merging #67 (d502ba4) into main (9d08f00) will not change coverage.
The diff coverage is n/a.

❗ Current head d502ba4 differs from pull request most recent head 701c883. Consider uploading reports for the commit 701c883 to get more accurate results

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   54.36%   54.36%           
=======================================
  Files           3        3           
  Lines         837      837           
  Branches       55       55           
=======================================
  Hits          455      455           
  Misses        382      382           

@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from ec8cee4 to 67aeed7 Compare April 4, 2023 02:27
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from a1a59a2 to 708f01f Compare April 10, 2023 01:07
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 3 times, most recently from bdad859 to 4bd6765 Compare April 24, 2023 01:36
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 9dd196f to d0aeadf Compare May 15, 2023 02:38
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 3e9c125 to 3a78649 Compare June 5, 2023 17:25
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 0103a3b to 2f82966 Compare June 26, 2023 02:23
@renovate renovate bot force-pushed the renovate/pnpm-8.x branch 2 times, most recently from 2d6ab46 to 3b48d63 Compare July 3, 2023 14:59
@renovate renovate bot changed the title chore(deps): update pnpm to v8 chore(deps): update pnpm to v8 - autoclosed Jul 17, 2023
@renovate renovate bot closed this Jul 17, 2023
@renovate renovate bot deleted the renovate/pnpm-8.x branch July 17, 2023 14:29
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

0 participants