Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/google/pprof-nodejs).

## Config Migration Needed

- [ ] Select this checkbox to let Renovate create an automated Config Migration PR.

## Deprecations / Replacements
> [!WARNING]
The following dependencies are either deprecated or have replacements available.

| Datasource | Package | Replacement PR? |
|------------|------|--------------|
| npm | [@types/p-limit](https://redirect.github.com/sindresorhus/p-limit) |  |
| npm | [@types/pretty-ms](https://redirect.github.com/sindresorhus/pretty-ms) |  |
| npm | [codecov](https://redirect.github.com/codecov/codecov-node) |  |

## Rate-Limited

The following updates are currently rate-limited. To force their creation now, click on a checkbox below.

- [ ] chore(deps): update dependency @types/node to v22
- [ ] chore(deps): update dependency linkinator to v8
- [ ] chore(deps): update dependency mocha to v12
- [ ] 🔐 **Create all rate-limited PRs at once** 🔐

## Open

The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.

- [ ] [chore(deps): update dependency protobufjs to v7.6.5 [security]](../pull/357)
- [ ] [chore(deps): update debian docker tag to trixie-20260824](../pull/354)
- [ ] [chore(deps): update golang docker tag to v1.27](../pull/360)
- [ ] [chore(deps): update actions/setup-node action to v7](../pull/355)
- [ ] [chore(deps): update codecov/codecov-action action to v7](../pull/342)
- [ ] [chore(deps): update dependency gts to v7](../pull/343)
- [ ] [chore(deps): update dependency protobufjs-cli to v2](../pull/345)
- [ ] [chore(deps): update dependency typescript to v7](../pull/356)
- [ ] [chore(deps): update node.js to v24](../pull/349)
- [ ] [fix(deps): update dependency delay to v7](../pull/351)
- [ ] [fix(deps): update dependency p-limit to v7](../pull/326)
- [ ] **Click on this checkbox to rebase all open PRs at once**

## Detected Dependencies

dockerfile (4)

system-test/Dockerfile.linux (2)

- `golang 1.24-bullseye`
- `debian trixie-20260623` → [Updates: `13`]

system-test/Dockerfile.node-alpine (1)

- `golang 1.26-alpine` → [Updates: `1.27-alpine`]

tools/build/Dockerfile.alpine (1)

- `node 20-alpine` → [Updates: `24-alpine`]

tools/build/Dockerfile.linux (1)

- `node 20-bookworm` → [Updates: `24-bookworm`]

github-actions (1)

.github/workflows/ci.yaml (5)

- `actions/setup-node v6` → [Updates: `v7`]
- `actions/checkout v7`
- `codecov/codecov-action v4` → [Updates: `v7`]
- `actions/setup-node v6` → [Updates: `v7`]
- `actions/checkout v7`

npm (3)

package.json (29)

- `bindings ^1.2.1`
- `delay ^5.0.0` → [Updates: `^7.0.0`]
- `findit2 ^2.2.3`
- `nan ^2.22.0`
- `p-limit ^3.0.0` → [Updates: `^7.0.0`]
- `protobufjs ~7.6.4` → [Updates: `~7.6.4`]
- `source-map ~0.8.0-beta.0`
- `split ^1.0.1`
- `@types/mocha ^10.0.0`
- `@types/node ^16.0.0` → [Updates: `^22.0.0`]
- `@types/p-limit ^2.0.0`
- `@types/pretty-ms ^5.0.0`
- `@types/request ^2.47.1`
- `@types/sinon ^22.0.0`
- `@types/tmp 0.2.6`
- `codecov ^3.0.0`
- `deep-copy ^1.4.2`
- `gts ^5.3.1` → [Updates: `^7.0.0`]
- `js-green-licenses ^4.0.0`
- `linkinator ^7.0.0` → [Updates: `^8.0.0`]
- `mocha ^11.0.0` → [Updates: `^12.0.0`]
- `nyc ^18.0.0`
- `protobufjs-cli 1.3.3` → [Updates: `2.7.0`]
- `sinon ^22.0.0`
- `source-map-support ^0.5.12`
- `tmp 0.2.7`
- `ts-mockito ^2.2.5`
- `typescript ^5.1.6` → [Updates: `^7.0.0`]
- `node >=18.0.0`

system-test/busybench-js/package.json

system-test/busybench/package.json

---

- [ ] Check this box to trigger a request for Renovate to run again on this repository

Questo è un dashboard Renovate automatizzato, non una singola attività. Esamina package.json, system-test/Dockerfile.linux, system-test/Dockerfile.node-alpine, tools/build/Dockerfile.alpine, tools/build/Dockerfile.linux e .github/workflows/ci.yaml, quindi controlla le PR delle dipendenze esistenti. Il lavoro è completo solo quando è stato selezionato e convalidato un aggiornamento specifico e l’elemento corrispondente del dashboard o la PR è stato risolto.

Scritto dal modello di indicizzazione a partire dal testo della issue.