Skip to content

ci(workflow): force gitleaks-action onto Node.js 24 + drop invalid 'fail' input #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pcalnon merged 1 commit into from
May 6, 2026
Merged

ci(workflow): force gitleaks-action onto Node.js 24 + drop invalid 'fail' input #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -380,8 +380,15 @@ jobs:
uses: gitleaks/gitleaks-action@ff98106e4c7b2bc287b24eaf42907196329070c7 # v2.3.9
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
fail: true
# gitleaks-action v2.3.9 ships as a Node.js 20 action.
# GitHub forces Node 24 on 2026-06-02; opt in now to eliminate
# the deprecation warning and ensure continued operation past
# the cutover. Drop this once gitleaks-action publishes a
# release pinned to node24 (upstream PR #215).
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
# gitleaks-action v2.3.9 has no `fail` input — passing it triggers
# "Unexpected input(s) 'fail'" warnings in CI. The action exits
# non-zero on leaks by default, which is the behavior we want.

- name: Set up Python
uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6.2.0
Expand Down
Loading