ci: bump gitleaks/gitleaks-action from 2.3.9 to 3.0.0#212
ci: bump gitleaks/gitleaks-action from 2.3.9 to 3.0.0#212dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [gitleaks/gitleaks-action](https://github.com/gitleaks/gitleaks-action) from 2.3.9 to 3.0.0. - [Release notes](https://github.com/gitleaks/gitleaks-action/releases) - [Commits](gitleaks/gitleaks-action@ff98106...e0c47f4) --- updated-dependencies: - dependency-name: gitleaks/gitleaks-action dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #212 +/- ##
=======================================
Coverage 99.40% 99.40%
=======================================
Files 33 33
Lines 1859 1859
Branches 513 530 +17
=======================================
Hits 1848 1848
Misses 9 9
Partials 2 2 Continue to review full report in Codecov by Sentry.
|
|
@dependabot rebase |
|
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
|
@coderabbitai review |
✅ Action performedReview finished.
|
📝 Walkthrough
WalkthroughThe GitHub Actions workflow file updates the pinned ChangesGitleaks Action Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/gitleaks.yml (1)
44-50:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winStale comment and unnecessary env var after v3.0.0 upgrade.
The comment references v2.3.9 and mentions "revisit when a successor lands"—v3.0.0 is that successor. Since v3.0.0 runs on Node 24 natively,
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24is no longer needed and the comment is now misleading.🧹 Proposed cleanup
- name: Run gitleaks uses: gitleaks/gitleaks-action@e0c47f4f8be36e29cdc102c57e68cb5cbf0e8d1e # v3.0.0 env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - # gitleaks-action v2.3.9 declares `runs.using: node20`, which - # GitHub will force to node24 by default starting 2026-06-02 - # and remove node20 entirely 2026-09-16. Opt into node24 now - # to silence the deprecation warning and validate compatibility - # before the forced flip. Upstream has not cut a node24 release - # since v2.3.9 (2025-04-17); revisit when a successor lands. - FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/gitleaks.yml around lines 44 - 50, The comment and the environment variable FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 are now stale after upgrading gitleaks to v3.0.0 (which already uses Node 24); remove the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 entry and the surrounding explanatory comment block in the gitleaks GitHub Actions workflow so the file no longer contains misleading text about v2.3.9 and node20/node24 compatibility.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In @.github/workflows/gitleaks.yml:
- Around line 44-50: The comment and the environment variable
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 are now stale after upgrading gitleaks to
v3.0.0 (which already uses Node 24); remove the
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 entry and the surrounding explanatory comment
block in the gitleaks GitHub Actions workflow so the file no longer contains
misleading text about v2.3.9 and node20/node24 compatibility.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 4b9e9f0a-a07b-4f27-aab2-f3cf4bd6bf49
📒 Files selected for processing (1)
.github/workflows/gitleaks.yml
1 participant
Bumps gitleaks/gitleaks-action from 2.3.9 to 3.0.0.
Release notes
Sourced from gitleaks/gitleaks-action's releases.
Commits
e0c47f4chore: migrate to Node 24 runtime (v3)bf2dc8eMerge pull request #191 from Olexandr88/patch-1b71323bUpdate README.md9c66aa9Update README.md186c3feCreate FUNDING.ymlDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)