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.33.5 - autoclosed #3

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 5, 2022

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

v7.33.5

Compare Source

v7.33.4

Compare Source

Patch Changes

  • When the same file is appended multiple times into a tarball, the last occurrence is selected when unpacking the tarball.
  • Added support for publishConfig.registry in package.json for publishing #​6775.
  • 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

Our Gold Sponsors

Our Silver Sponsors

v7.33.3

Compare Source

Patch Changes

  • Improve the performance of searching for auth tokens.
  • 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.

Our Gold Sponsors

Our Silver Sponsors

v7.33.2

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.
  • 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.
  • Ignore the port in the URL, while searching for authentication token in the .npmrc file #​6354.
  • Throw a meaningful error when applying a patch to a dependency fails.
  • pnpm update --global --latest should work #​3779.

Our Gold Sponsors

Our Silver Sponsors

v7.33.1

Compare Source

Patch Changes
  • When dedupe-peer-dependents is enabled, 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

  • Change lockfile version back to 6.0 as previous versions of pnpm fail to parse the version correctly.

Our Gold Sponsors
Our Silver Sponsors

v7.33.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

Patch Changes

  • 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.
  • Should respect ignore patterns in updateConfig.ignoreDependencies #​6548

Our Gold Sponsors

Our Silver Sponsors

v7.32.5

Compare Source

Patch Changes

  • pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
  • Expanded missing command error, including 'did you mean' #​6492.
  • Normalize current working directory on Windows #​6524.
  • Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v7.32.4

Compare Source

Patch Changes

  • pnpm link -g <pkg-name> should not modify the package.json file #​4341.
  • Node.js range specified through the engines field should match prerelease versions #​6509.
  • pnpm publish --otp should work #​6514.

Our Gold Sponsors

Our Silver Sponsors

v7.32.3

Compare Source

Patch Changes

  • Link the bin files of local workspace dependencies, when node-linker is set to hoisted 6486.
  • Show cyclic workspace dependency details #​5059.

Our Gold Sponsors

Our Silver Sponsors

v7.32.2

Compare Source

Patch Changes

  • Patch node-fetch to fix an error that happens on Node.js 20 #​6424.

Our Gold Sponsors

Our Silver Sponsors

v7.32.1

Compare Source

Patch Changes

  • Warn user when publishConfig.directory of an injected workspace dependency does not exist #​6396.
  • Use hard links to link the node executable on Windows machines #​4315.

Our Gold Sponsors

Our Silver Sponsors

v7.32.0

Compare Source

Minor Changes

  • Allow env variables to be specified with default values in .npmrc. This is a convention used by Yarn too.
    Using ${NAME-fallback} will return fallback if NAME isn't set. ${NAME:-fallback} will return fallback if NAME isn't set, or is an empty string #​6018.

Patch Changes

  • pnpm config get <key> returns empty when the value is a boolean
  • Don't print an info message about linked dependencies if they are real linked dependencies specified via the link: protocol in package.json.
  • Add -g to mismatch registries error info when original command has -g option #​6224.

Our Gold Sponsors

Our Silver Sponsors

v7.31.0

Compare Source

Minor Changes

  • Add ignore-workspace-cycles to silence workspace cycle warning #​6308.
Patch Changes
  • Registries are now passed to the preResolution hook.
  • Repeat installation should work on a project that has a dependency with () chars in the scope name #​6348.
  • Should report error summary as expected.
  • Update @yarnpkg/shell to fix issues in the shell emulator #​6320.
  • Installation should not fail when there is a local dependency that starts in a directory that starts with the @ char #​6332.

Our Gold Sponsors

Our Silver Sponsors

v7.30.5

Compare Source

Patch Changes

  • pnpm audit should work even if there are no package.json file, just a pnpm-lock.yaml file.
  • Dedupe direct dependencies after hoisting.
  • Don't remove automatically installed peer dependencies from the root workspace project, when dedupe-peer-dependents is true #​6154.

Our Gold Sponsors

Our Silver Sponsors

v7.30.4

Compare Source

v7.30.3

Compare Source

Patch Changes

  • Should use most specific override rule when multiple rules match the same target #​6210.
  • Fix regression introduced in v7.30.1 #​6271.

Our Gold Sponsors

Our Silver Sponsors

v7.30.2

Compare Source

v7.30.1

Compare Source

Patch Changes

  • Don't write the pnpm-lock.yaml file if it has no changes and pnpm install --frozen-lockfile was executed #​6158.
  • Fix git-hosted dependencies referenced via git+ssh that use semver selectors #​6239.
  • When publish some package throws an error, the exit code should be non-zero #​5528.
  • Only three paths are displayed in pnpm audit output #​6203
  • Aliased packages should be used to resolve peer dependencies too #​4301.

Our Gold Sponsors

Our Silver Sponsors

v7.30.0

Compare Source

Minor Changes

  • Allow to set a custom directory for storing patch files via the patches-dir setting #​6215

Patch Changes

  • New directories should be prepended to NODE_PATH in command shims, not appended.
  • Retry copying file on EBUSY error #​6201.

Our Gold Sponsors

Our Silver Sponsors

v7.29.3

Compare Source

Patch Changes

  • Command shim should not set higher priority to the node_modules/.pnpm/node_modules directory through the NODE_PATH env variable, then the command's own node_modules directory #​5176.
  • extend-node-path is set back to true by default. It was set to false in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extending NODE_PATH. We have fixed the Jest issue with a different solution #​6213.

Our Gold Sponsors


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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 v7.1.8 chore(deps): update pnpm to v7.1.9 Jun 6, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.1.9 chore(deps): update pnpm to v7.2.0 Jun 10, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.2.0 chore(deps): update pnpm to v7.2.1 Jun 11, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.2.1 chore(deps): update pnpm to v7.3.0 Jun 19, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.3.0 chore(deps): update pnpm to v7.4.0 Jun 28, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.4.0 chore(deps): update pnpm to v7.4.1 Jun 30, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.4.1 chore(deps): update pnpm to v7.5.0 Jul 2, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.5.0 chore(deps): update pnpm to v7.5.1 Jul 12, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.5.1 chore(deps): update pnpm to v7.5.2 Jul 16, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.5.2 chore(deps): update pnpm to v7.6.0 Jul 22, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.6.0 chore(deps): update pnpm to v7.7.0 Jul 29, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.7.0 chore(deps): update pnpm to v7.7.1 Jul 30, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.7.1 chore(deps): update pnpm to v7.8.0 Jul 31, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.8.0 chore(deps): update pnpm to v7.12.2 Sep 25, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.12.2 chore(deps): update pnpm to v7.15.0 Nov 12, 2022
@renovate renovate bot changed the title chore(deps): update pnpm to v7.23.0 chore(deps): update pnpm to v7.24.2 Jan 10, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.24.2 chore(deps): update pnpm to v7.24.3 Jan 11, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.24.3 chore(deps): update pnpm to v7.25.0 Jan 13, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.25.0 chore(deps): update pnpm to v7.29.3 Mar 17, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.29.3 chore(deps): update pnpm to v7.30.0 Mar 22, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.30.0 chore(deps): update pnpm to v7.30.5 Mar 27, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.30.5 chore(deps): update pnpm to v7.32.5 May 28, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.32.5 chore(deps): update pnpm to v7.33.0 Jun 1, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.33.0 chore(deps): update pnpm to v7.33.1 Jun 16, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.33.1 chore(deps): update pnpm to v7.33.2 Jun 24, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.33.2 chore(deps): update pnpm to v7.33.3 Jul 1, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.33.3 chore(deps): update pnpm to v7.33.4 Jul 17, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.33.4 chore(deps): update pnpm to v7.33.5 Jul 18, 2023
@renovate renovate bot changed the title chore(deps): update pnpm to v7.33.5 chore(deps): update pnpm to v7.33.5 - autoclosed Aug 3, 2023
@renovate renovate bot closed this Aug 3, 2023
@renovate renovate bot deleted the renovate/pnpm-7.x branch August 3, 2023 13:23
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