Skip to content

chore(deps): update all dependencies#124

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-dependencies
Open

chore(deps): update all dependencies#124
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-dependencies

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 21, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Pending Age Confidence
node (source) minor 24.15.024.16.0 age confidence
npm:pnpm (source) minor 11.2.211.3.0 11.5.0 (+1) age confidence
pnpm (source) packageManager minor 11.2.2+sha512.36e6621fad506178936455e70247b8808ef4ec25797a9f437a93281a020484e2607f6a469a22e982987c3dbb8866e3071514ab10a4a1749e06edcd1ec118436f11.3.0 11.5.0 (+1) age confidence
quay.io/pypa/manylinux_2_28 final digest 65f13b3f135790
rust (source, changelog) toolchain patch nightly-2026-05-24nightly-2026-05-25 nightly-2026-05-31 (+5) age confidence

Release Notes

nodejs/node (node)

v24.16.0: 2026-05-21, Version 24.16.0 'Krypton' (LTS), @​aduh95

Compare Source

Notable Changes
  • [b267f6bca3] - (SEMVER-MINOR) crypto: implement randomUUIDv7() (nabeel378) #​62553
  • [ec2451b9cd] - (SEMVER-MINOR) debugger: add edit-free runtime expression probes to node inspect (Joyee Cheung) #​62713
  • [9705f628d9] - (SEMVER-MINOR) fs: add signal option to fs.stat() (Mert Can Altin) #​57775
  • [40ccfdecf9] - (SEMVER-MINOR) fs: expose frsize field in statfs (Jinho Jang) #​62277
  • [d7188af5c9] - (SEMVER-MINOR) http: harden ClientRequest options merge (Matteo Collina) #​63082
  • [aa1d8a9afc] - (SEMVER-MINOR) http: add req.signal to IncomingMessage (Akshat) #​62541
  • [6f37f7e240] - (SEMVER-MINOR) stream: propagate destruction in duplexPair (Ahmed Elhor) #​61098
  • [d14029be7f] - (SEMVER-MINOR) test_runner: support test order randomization (Pietro Marchini) #​61747
  • [d142c584cd] - (SEMVER-MINOR) test_runner: align mock timeout api (sangwook) #​62820
  • [01a9552585] - (SEMVER-MINOR) test_runner: add mock-timers support for AbortSignal.timeout (DeveloperViraj) #​60751
  • [00705a459a] - (SEMVER-MINOR) util: colorize text with hex colors (Guilherme Araújo) #​61556
Commits
pnpm/pnpm (npm:pnpm)

v11.3.0

Compare Source

Minor Changes
  • Added pnpm stage with publish, list, view, approve, reject, and download subcommands for npm staged publishing.

  • Added a new setting trustLockfile. When true, pnpm install skips the supply-chain verification pass that re-applies minimumReleaseAge / trustPolicy='no-downgrade' to every entry in the loaded lockfile. The install treats the lockfile as already-trusted — useful for closed-source projects where every commit comes from a trusted author. Defaults to false; verification stays on by default. Set in pnpm-workspace.yaml.

    Also cut the memory footprint of the verification pass itself: the per-(registry, name) trust-meta cache previously retained the full packument — dependency graphs, scripts, README, and per-version manifests — for the entire install. On large workspaces (~4k lockfile entries with minimumReleaseAge + trustPolicy: no-downgrade enabled) this could OOM CI runners with a 2GB heap cap. The cache now stores only the fields the trust check actually reads (time, per-version _npmUser.trustedPublisher, dist.attestations.provenance). The abbreviated-metadata cache is similarly projected to just the package-level modified field and the set of currently-listed version names. Fixes [#​1

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • "every weekend"
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Mar 21, 2026

⚠️ Artifact update problem

Renovate failed to update artifacts 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: mise.lock

mise ERROR error parsing config file: /tmp/renovate/repos/github/vadimpiven/node_reqwest/mise.toml
mise ERROR Config files in /tmp/renovate/repos/github/vadimpiven/node_reqwest/mise.toml are not trusted.
Trust them with `mise trust`. See https://mise.en.dev/cli/trust.html for more information.
mise ERROR Version: 2026.5.18 linux-x64 (2026-05-31)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

Command failed: mise lock node npm:pnpm
mise ERROR error parsing config file: /tmp/renovate/repos/github/vadimpiven/node_reqwest/mise.toml
mise ERROR Config files in /tmp/renovate/repos/github/vadimpiven/node_reqwest/mise.toml are not trusted.
Trust them with `mise trust`. See https://mise.en.dev/cli/trust.html for more information.
mise ERROR Version: 2026.5.18 linux-x64 (2026-05-31)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

File name: package.json
Command failed: corepack use pnpm@11.3.0

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Mar 21, 2026

Greptile Summary

This is a routine automated dependency update PR from Renovate Bot, bumping a wide range of dependencies across the stack: GitHub Actions (setup-node v6.3.0, mise-action v3.6.3, zizmor-action v0.5.2, codeql-action v4.32.6), Node.js packages (pnpm 10.32.1, vitest/vite 4.1.0/8.0.0 stable releases from beta, oxfmt, oxlint, undici, electron, node-addon-slsa), Rust crates (tempfile 3.27.0), Python tools (ruff, semgrep, pyrefly, zizmor), and various aqua-managed CLI tools (uv, gh, gitleaks, shfmt, nextest). All GitHub Action references continue to be pinned by full commit SHA, which is good practice for this repository.

  • Most changes are straightforward version bumps with no behavioral impact on the codebase itself.
  • Several beta versions (vitest, vite) graduate to stable releases — a positive change.
  • The packageManager field in package.json was updated to pnpm@10.32.1 but the SHA512 integrity hash that was present in the old value was dropped, removing Corepack's ability to verify the pnpm binary on download.

Confidence Score: 4/5

  • This PR is safe to merge; the only notable finding is a non-critical omission of the Corepack integrity hash for pnpm.
  • All changes are automated dependency bumps. GitHub Actions remain SHA-pinned, Dockerfile images are digest-pinned, and lock files are fully regenerated. The one notable point is the missing SHA512 hash in the packageManager field, which is a best-practice/supply-chain hygiene issue rather than an active vulnerability. Everything else is routine.
  • package.json — missing SHA512 hash in the packageManager field.

Important Files Changed

Filename Overview
package.json Updated pnpm to 10.32.1 but dropped the SHA512 integrity hash from the packageManager field, removing Corepack's ability to verify the binary's integrity on download.
Dockerfile Updated docker/dockerfile syntax to 1.22 and manylinux_2_28 base image to a new digest. Both references are pinned by SHA256. No issues found.
Cargo.lock Updated tempfile from 3.26.0 to 3.27.0 which pulls in getrandom 0.3.4 instead of 0.4.2, and resolves different windows-sys versions for various crates. Standard lock file update.
mise.toml Updated gitleaks, uv, gh CLI, nextest, and mvdan/sh (shfmt) to newer patch/minor versions. No issues found.
pyproject.toml Updated pyrefly, ruff, semgrep, and zizmor to newer versions. No issues found.
pnpm-workspace.yaml Updated catalog versions for @vitest/coverage-istanbul, electron, oxfmt, oxlint, undici, vite, and vitest from beta/older versions to stable releases. No issues found.

Comments Outside Diff (1)

  1. package.json, line 202 (link)

    P2 Missing Corepack integrity hash for pnpm

    The previous packageManager value included a +sha512 integrity hash that Corepack uses to cryptographically verify the pnpm binary on download. The new value omits this hash entirely, so Corepack will skip integrity verification when bootstrapping pnpm from this field.

    You can restore supply-chain integrity by running:

    corepack use pnpm@10.32.1

    This will update package.json with the correct hash for 10.32.1, e.g.:

    Consider asking Renovate to preserve the hash when bumping the packageManager field (the pinDigests option may help, or a custom packageRules entry targeting packageManager).

    Prompt To Fix With AI
    This is a comment left during a code review.
    Path: package.json
    Line: 202
    
    Comment:
    **Missing Corepack integrity hash for pnpm**
    
    The previous `packageManager` value included a `+sha512` integrity hash that Corepack uses to cryptographically verify the pnpm binary on download. The new value omits this hash entirely, so Corepack will skip integrity verification when bootstrapping pnpm from this field.
    
    You can restore supply-chain integrity by running:
    
    ```bash
    corepack use pnpm@10.32.1
    ```
    
    This will update `package.json` with the correct hash for 10.32.1, e.g.:
    
    
    
    Consider asking Renovate to preserve the hash when bumping the `packageManager` field (the [`pinDigests`](https://docs.renovatebot.com/configuration-options/#pindigests) option may help, or a custom `packageRules` entry targeting `packageManager`).
    
    How can I resolve this? If you propose a fix, please make it concise.
Prompt To Fix All With AI
This is a comment left during a code review.
Path: package.json
Line: 202

Comment:
**Missing Corepack integrity hash for pnpm**

The previous `packageManager` value included a `+sha512` integrity hash that Corepack uses to cryptographically verify the pnpm binary on download. The new value omits this hash entirely, so Corepack will skip integrity verification when bootstrapping pnpm from this field.

You can restore supply-chain integrity by running:

```bash
corepack use pnpm@10.32.1
```

This will update `package.json` with the correct hash for 10.32.1, e.g.:

```suggestion
  "packageManager": "pnpm@10.32.1+sha512.<hash-for-10.32.1>",
```

Consider asking Renovate to preserve the hash when bumping the `packageManager` field (the [`pinDigests`](https://docs.renovatebot.com/configuration-options/#pindigests) option may help, or a custom `packageRules` entry targeting `packageManager`).

How can I resolve this? If you propose a fix, please make it concise.

Last reviewed commit: "Update all dependenc..."

@renovate renovate Bot force-pushed the renovate/all-dependencies branch 4 times, most recently from 1c2d5e5 to 40653e4 Compare March 22, 2026 02:03
Comment thread .github/workflows/release.yaml Fixed
Comment thread .github/workflows/release.yaml Fixed
@renovate renovate Bot force-pushed the renovate/all-dependencies branch from 40653e4 to 757f335 Compare March 22, 2026 04:59
Comment thread .github/workflows/release.yaml Fixed
Comment thread .github/workflows/release.yaml Fixed
@renovate renovate Bot force-pushed the renovate/all-dependencies branch from 757f335 to a2c2755 Compare March 22, 2026 21:02
Comment thread .github/workflows/release.yaml Fixed
Comment thread .github/workflows/release.yaml Fixed
@renovate renovate Bot force-pushed the renovate/all-dependencies branch from a2c2755 to 4501313 Compare March 23, 2026 01:45
Comment thread .github/workflows/release.yaml Fixed
Comment thread .github/workflows/release.yaml Fixed
@renovate renovate Bot force-pushed the renovate/all-dependencies branch 17 times, most recently from c433c4d to 7fe5e47 Compare March 27, 2026 13:13
@renovate renovate Bot force-pushed the renovate/all-dependencies branch 2 times, most recently from 57dabdb to b7f6851 Compare April 19, 2026 09:14
Comment thread .github/workflows/release.yaml Fixed
Comment thread .github/workflows/release.yaml Fixed
@renovate renovate Bot force-pushed the renovate/all-dependencies branch 9 times, most recently from 5bce89e to 366fde0 Compare April 20, 2026 21:11
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate renovate Bot force-pushed the renovate/all-dependencies branch 9 times, most recently from e033171 to c00b714 Compare April 27, 2026 22:59
@renovate renovate Bot force-pushed the renovate/all-dependencies branch 6 times, most recently from 48dd3a8 to 5e27d67 Compare April 30, 2026 15:12
@codspeed-hq
Copy link
Copy Markdown

codspeed-hq Bot commented May 18, 2026

Merging this PR will not alter performance

✅ 15 untouched benchmarks


Comparing renovate/all-dependencies (8a7990e) with main (d3731e4)

Open in CodSpeed

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