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.11.0 #155

Merged
merged 1 commit into from
Sep 20, 2024
Merged

chore(deps): update pnpm to v9.11.0 #155

merged 1 commit into from
Sep 20, 2024

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 17, 2024

This PR contains the following updates:

Package Type Update Change OpenSSF
pnpm (source) packageManager minor 9.7.0 -> 9.11.0 OpenSSF Scorecard

Release Notes

pnpm/pnpm (pnpm)

v9.11.0

Compare Source

v9.10.0: pnpm 9.10

Compare Source

Minor Changes

  • Support for a new CLI flag, --exclude-peers, added to the list and why commands. When --exclude-peers is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #​8506.

  • Added a new setting to package.json at pnpm.auditConfig.ignoreGhsas for ignoring vulnerabilities by their GHSA code #​6838.

    For instance:

    {
      "pnpm": {
        "auditConfig": {
          "ignoreGhsas": [
            "GHSA-42xw-2xvc-qx8m",
            "GHSA-4w2v-q235-vp99",
            "GHSA-cph5-m8f7-6c5x",
            "GHSA-vh95-rmgr-6w4m"
          ]
        }
      }
    }

Patch Changes

  • Throw an exception if pnpm switches to the same version of itself.
  • Reduce memory usage during peer dependencies resolution.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.9.0

Compare Source

v9.8.0

Compare Source

v9.7.1

Compare Source


Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Copy link
Author

renovate bot commented Apr 17, 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 14 projects
undefined
/tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/manifest/repo/node/pkg2:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@node%2Fpkg1: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/manifest/repo/node/pkg2

@node/pkg1 is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.
undefined

@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 4 times, most recently from b5f7e09 to 0e5adad Compare April 24, 2024 14:03
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 10 times, most recently from 43bb553 to dd7d282 Compare May 13, 2024 00:24
Copy link
Author

renovate bot commented May 13, 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 14 projects
undefined
/tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@here%2FpkgA: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace

@here/pkgA is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.
undefined

@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 6ceecba to adf40e9 Compare May 27, 2024 10:32
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 3fb9a1a to 9c9459d Compare June 5, 2024 17:21
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 3a044d9 to 906740a Compare July 24, 2024 21:13
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 4 times, most recently from bdbfa1f to d697ea4 Compare August 9, 2024 01:59
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 2b08a99 to aa779b3 Compare August 26, 2024 17:11
@renovate renovate bot force-pushed the renovate/pnpm-9.x branch 2 times, most recently from 5c21977 to 9af28ab Compare September 9, 2024 18:49
@renovate renovate bot enabled auto-merge September 9, 2024 18:49
@renovate renovate bot changed the title chore(deps): update pnpm to v9 chore(deps): update pnpm to v9.10.0 Sep 9, 2024
@renovate renovate bot changed the title chore(deps): update pnpm to v9.10.0 chore(deps): update pnpm to v9.11.0 Sep 20, 2024
@renovate renovate bot added this pull request to the merge queue Sep 20, 2024
Merged via the queue into main with commit 6798504 Sep 20, 2024
4 of 5 checks passed
@renovate renovate bot deleted the renovate/pnpm-9.x branch September 20, 2024 11:34
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