chore(deps): bump gitleaks/gitleaks-action from 2.3.9 to 3.0.0

[dependabot]

Bumps gitleaks/gitleaks-action from 2.3.9 to 3.0.0.

Release notes

Sourced from gitleaks/gitleaks-action's releases.

v3.0.0

What's changed

gitleaks-action v3 migrates the runtime from Node 20 to Node 24. No changes to inputs, outputs, or behavior. Update your workflow from gitleaks/gitleaks-action@v2 to gitleaks/gitleaks-action@v3.

Migration

# Before
- uses: gitleaks/gitleaks-action@v2
After

uses: gitleaks/gitleaks-action@v3

Why

GitHub is deprecating the Node 20 runtime for Actions:

• June 2, 2026: GitHub flips the runner default to Node 24. Workflows using gitleaks-action@v2 (Node 20) will still run, but only if ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true is set as an environment variable.
• September 16, 2026: Node 20 is removed from GitHub-hosted runners entirely. gitleaks-action@v2 stops working regardless of any opt-out flag.

Changes

• action.yml: runtime node20 → node24
• @actions/core: 1.10.0 → 1.11.1
• dist/ rebuilt
• Example workflows updated to actions/checkout@v6 and gitleaks-action@v3
• README updated with v3 migration guide

Self-hosted runners

If you use self-hosted runners, ensure your runner version is >= v2.327.1 (required for Node 24 support).

Commits

• e0c47f4 chore: migrate to Node 24 runtime (v3)
• bf2dc8e Merge pull request #191 from Olexandr88/patch-1
• b71323b Update README.md
• 9c66aa9 Update README.md
• 186c3fe Create FUNDING.yml
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
do-knowledge-studio	Ready	Preview, v0	Aug 18, 2026 4:50am

[github-actions]

Blocked merge diagnosis — blocked
⏳ Check run(s) still in progress: ["Unit Tests","Quality Gate","Codacy Static Code Analysis","Diagnose Blocked Merge State","Infrastructure as Code Security","Trivy Filesystem Security Scan","GitHub Actions Workflow Validation","Shell Script Security Analysis","Secret Detection","YAML Syntax Validation"]

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[d-oit]

🔥 Roast & verdict: CLOSE (this is a regression, not an upgrade)

Dependabot, this is the third time you've tried to hand me a footgun. 🎯

What it does: bumps gitleaks/gitleaks-action from v2.3.9 → v3.0.0.

Why it's a trap: This repo already fixed this exact failure in PR #643 / plans/115. The workflow file you're editing literally has a comment one line above your diff saying:

# v2.3.9 pinned: v3+ requires a paid GITLEAKS_LICENSE secret.

The release notes' claim that v3 has "no changes to inputs, outputs, or behavior" is technically cute but irrelevant — the behavior that matters (the license gate) is unchanged in v3, and this is an organization-owned repo (d-oit), where the official action README states:

GITLEAKS_LICENSE — required for organizations, not required for user accounts.

There is no GITLEAKS_LICENSE secret configured (gh secret list confirms), so merging this re-breaks Secret Detection exactly the way plans/115 already diagnosed: 🛑 missing gitleaks license.

Verdict: Negative value. Reverts a documented maintainer decision. Closing.

@dependabot ignore this major version

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.