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 v9.5.0 #2544

Merged
merged 1 commit into from
Jul 8, 2024
Merged

chore(deps): update pnpm to v9.5.0 #2544

merged 1 commit into from
Jul 8, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2024

Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

v9.5.0

Compare Source

v9.4.0

Compare Source

v9.3.0

Compare Source

Minor Changes

  • Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the peers-suffix-max-length setting #​8177.

Patch Changes

  • Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter-hide-prefix=false #​8174.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.2.0

Compare Source

Minor Changes

  • If package-manager-strict-version is set to true, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of package.json.

Patch Changes

  • Update @yarnpkg/pnp to the latest version, fixing issue with node: imports #​8161.
  • Deduplicate bin names to prevent race condition and corrupted bin scripts #​7833.
  • pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of package.json #​8087.
  • exec now also streams prefixed output when --recursive or --parallel is specified just as run does #​8065.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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.


Mend Renovate

This PR contains the following updates:

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

Release Notes

pnpm/pnpm (pnpm)

v9.5.0

Compare Source

v9.4.0

Compare Source

v9.3.0

Compare Source

Minor Changes

  • Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the peers-suffix-max-length setting #​8177.

Patch Changes

  • Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter-hide-prefix=false #​8174.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.2.0

Compare Source

Minor Changes

  • If package-manager-strict-version is set to true, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of package.json.

Patch Changes

  • Update @yarnpkg/pnp to the latest version, fixing issue with node: imports #​8161.
  • Deduplicate bin names to prevent race condition and corrupted bin scripts #​7833.
  • pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of package.json #​8087.
  • exec now also streams prefixed output when --recursive or --parallel is specified just as run does #​8065.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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.

Copy link
Contributor Author

renovate bot commented Jun 1, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 8 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/walinejs/waline/packages/client:
 ERR_PNPM_NO_MATCHING_VERSION_INSIDE_WORKSPACE  In packages/client: No matching version found for @waline/api@workspace:1.0.0-alpha.7 inside the workspace

This error happened while installing a direct dependency of /tmp/renovate/repos/github/walinejs/waline/packages/client

@renovate renovate bot changed the title chore(deps): update pnpm to v9.1.4 chore(deps): update pnpm to v9.1.4 - autoclosed Jun 5, 2024
@renovate renovate bot closed this Jun 5, 2024
@renovate renovate bot deleted the renovate/pnpm-9.x branch June 5, 2024 10:47
@renovate renovate bot changed the title chore(deps): update pnpm to v9.1.4 - autoclosed chore(deps): update pnpm to v9.1.4 Jun 5, 2024
@renovate renovate bot reopened this Jun 5, 2024
@renovate renovate bot restored the renovate/pnpm-9.x branch June 5, 2024 14:00
@renovate renovate bot changed the title chore(deps): update pnpm to v9.1.4 chore(deps): update pnpm to v9.2.0 Jun 5, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 82423e0 to 332b36a Compare June 5, 2024 16:24
@renovate renovate bot changed the title chore(deps): update pnpm to v9.2.0 chore(deps): update pnpm to v9.3.0 Jun 10, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 332b36a to d4663ab Compare June 10, 2024 14:04
@renovate renovate bot changed the title chore(deps): update pnpm to v9.3.0 chore(deps): update pnpm to v9.4.0 Jun 17, 2024
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from d4663ab to 9b35f06 Compare June 17, 2024 19:52
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch from 9b35f06 to 7af54b3 Compare July 7, 2024 16:54
@renovate renovate bot changed the title chore(deps): update pnpm to v9.4.0 chore(deps): update pnpm to v9.5.0 Jul 7, 2024
@Mister-Hope Mister-Hope merged commit 0c6204a into main Jul 8, 2024
12 checks passed
@Mister-Hope Mister-Hope deleted the renovate/pnpm-9.x branch July 8, 2024 03:28
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