gitleaks-action v2 deprecation — migrate to v3 before September 2026

## v2 Deprecation Notice

`gitleaks-action@v2` uses the Node 20 runtime, which GitHub is deprecating on the following schedule:

| Date | What happens |
|------|-------------|
| **June 2, 2026** | GitHub flips the runner default to Node 24. `@v2` workflows will require `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true` to continue running. |
| **September 16, 2026** | Node 20 is removed from GitHub-hosted runners. `@v2` stops working entirely. |

## How to migrate

Update your workflow:

```yaml
# Before
- uses: gitleaks/gitleaks-action@v2

# After
- uses: gitleaks/gitleaks-action@v3
```

There are no changes to inputs, outputs, or behavior. The only difference is the Node runtime version.

## Temporary workaround

If you cannot upgrade immediately, add this environment variable to your workflow to keep `@v2` working until September 16:

```yaml
env:
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true
```

## Self-hosted runners

If you use self-hosted runners, ensure your runner version is `>= v2.327.1` before switching to `@v3`.

## Timeline

We recommend migrating to `@v3` as soon as possible. `@v2` will not receive further updates.

See the [v3.0.0 release notes](https://github.com/gitleaks/gitleaks-action/releases/tag/v3.0.0) for full details.

Locate the workflow files containing `gitleaks/gitleaks-action@v2` and read the surrounding job configuration, including any self-hosted runner settings. Replace the action reference with `@v3`, confirm self-hosted runners meet the stated version when applicable, and verify the workflow completes successfully without the temporary environment variable.

Written by the indexing model from the issue text.