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/adobe/helix-google-support).

## Config Migration Needed

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

## Awaiting Schedule

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

- [ ] chore(deps): update dependency lint-staged to v17.4.1

## Pending Status Checks

The following updates await pending status checks. To force their creation now, click on a checkbox below.

- [ ] chore(deps): update dependency mocha to v12

## Detected Dependencies

github-actions (2)

.github/workflows/main.yaml (7)

- `actions/checkout v7`
- `actions/setup-node v7`
- `codecov/codecov-action v7`
- `actions/checkout v7`
- `actions/setup-node v7`
- `node 24.x`
- `node 24.x`

.github/workflows/semver-check.yaml (1)

- `adobe-rnd/github-semantic-release-comment-action main`

npm (1)

package.json (22)

- `@adobe/helix-shared-string ^2.1.0`
- `googleapis 150.0.1`
- `googleapis-common 9.0.4`
- `lru-cache ^11.0.2`
- `@adobe/eslint-config-helix 3.0.31`
- `@adobe/helix-shared-tokencache 1.6.2`
- `@eslint/config-helpers 0.7.0`
- `@semantic-release/changelog 7.0.0`
- `@semantic-release/git 11.0.1`
- `c8 12.0.0`
- `dotenv 17.4.2`
- `eslint 9.39.5`
- `eslint-plugin-header 3.1.1`
- `eslint-plugin-import 2.32.0`
- `husky 9.1.7`
- `junit-report-builder 5.1.2`
- `lint-staged 17.3.0` → [Updates: `17.4.1`]
- `mocha 11.8.0` → [Updates: `12.0.1`]
- `mocha-multi-reporters 1.5.1` → [Updates: `1.5.2`]
- `mocha-suppress-logs 0.6.0`
- `nock 14.0.17`
- `semantic-release 25.0.9`

renovate-config (1)

.renovaterc.json

---

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

This is an automated Renovate dashboard rather than a scoped code task. Read the Renovate dashboard documentation, then inspect package.json, .renovaterc.json, and the listed GitHub Actions workflows; use the relevant checkbox to trigger or approve an update. Done means the selected dependency update is created successfully and the repository checks pass.

Written by the indexing model from the issue text.