Dependency Dashboard

Dieses Issue hat noch niemand übernommen.

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/loopbackio/strong-error-handler).

## Awaiting Schedule

The following updates are awaiting their schedule. To get an update now, click on a checkbox below.

- [ ] chore: lock file maintenance

## Open

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

- [ ] [chore: update github/codeql-action action to v4.38.1](../pull/762)
- [ ] [chore: update dependency http-status to v2](../pull/443)
- [ ] [chore: update lint packages (major)](../pull/540) (`eslint`, `eslint-config-loopback`, `eslint-plugin-mocha`)
- [ ] **Click on this checkbox to rebase all open PRs at once**

## PR Closed (Blocked)

The following updates are blocked by an existing closed PR. To recreate the PR, click on a checkbox below.

- [ ] [chore: update dependency node to v24](../pull/636)

## Detected Dependencies

github-actions (3)

.github/workflows/codeql-analysis.yml (3)

- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `github/codeql-action v4.38.0@b96794f015dfd88f77b49b1c93e0fa7110f94c63` → [Updates: `v4.38.1`]
- `github/codeql-action v4.38.0@b96794f015dfd88f77b49b1c93e0fa7110f94c63` → [Updates: `v4.38.1`]

.github/workflows/continuous-integration.yml (16)

- `step-security/harden-runner v2.21.1@e14015d583714f6e62063499dc959a02595150a1`
- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `actions/setup-node v7.0.0@820762786026740c76f36085b0efc47a31fe5020`
- `Yuri6037/Action-FakeTTY v1.1@1abc69c7d530815855caedcd73842bae5687c1a6`
- `step-security/harden-runner v2.21.1@e14015d583714f6e62063499dc959a02595150a1`
- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `actions/setup-node v7.0.0@820762786026740c76f36085b0efc47a31fe5020`
- `step-security/harden-runner v2.21.1@e14015d583714f6e62063499dc959a02595150a1`
- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `actions/setup-node v7.0.0@820762786026740c76f36085b0efc47a31fe5020`
- `step-security/harden-runner v2.21.1@e14015d583714f6e62063499dc959a02595150a1`
- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `actions/setup-node v7.0.0@820762786026740c76f36085b0efc47a31fe5020`
- `node 22.23.2` → [Updates: `24.21.0`]
- `node 22.23.2` → [Updates: `24.21.0`]
- `node 22.23.2` → [Updates: `24.21.0`]

.github/workflows/scorecards.yml (5)

- `step-security/harden-runner v2.21.1@e14015d583714f6e62063499dc959a02595150a1`
- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `ossf/scorecard-action v2.4.4@2d1146689b8cda280b9bc96326124645441f03bc`
- `actions/upload-artifact v7.0.1@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a`
- `github/codeql-action v4.38.0@b96794f015dfd88f77b49b1c93e0fa7110f94c63` → [Updates: `v4.38.1`]

npm (1)

package.json (19)

- `accepts ^1.3.8`
- `debug ^4.4.3`
- `fast-safe-stringify ^2.1.1`
- `handlebars ^4.7.9`
- `http-status ^1.8.1` → [Updates: `^2.1.0`]
- `js2xmlparser ^5.0.0`
- `strong-globalize ^6.0.6`
- `@commitlint/cli ^21.2.2`
- `@commitlint/config-conventional ^21.2.2`
- `@eslint/eslintrc ^3.3.7`
- `@types/express ^5.0.6`
- `chai ^6.2.2`
- `eslint ^9.39.5` → [Updates: `^10.11.0`]
- `eslint-config-loopback ^13.1.0` → [Updates: `^14.0.0`]
- `eslint-plugin-mocha ^10.5.0` → [Updates: `^12.0.2`]
- `express ^5.2.1`
- `lockfile-lint ^5.0.1`
- `mocha ^12.0.2`
- `supertest ^7.2.2`

renovate-config (1)

renovate.json

---

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

Beginnen Sie mit dem Dependency Dashboard und untersuchen Sie package.json sowie die aufgeführten Dateien unter .github/workflows. Prüfen Sie die verknüpften Renovate-Pull-Requests und die ausstehenden Update-Einträge, bevor Sie entscheiden, ob ein Update noch bearbeitbar ist; abgeschlossen bedeutet, dass das ausgewählte Dependency- oder Action-Update abgeschlossen ist und seine Checks erfolgreich sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.