ci(workflow): force gitleaks-action onto Node.js 24#91
Merged
Conversation
GitHub forces all Node.js 20 actions onto Node.js 24 on 2026-06-02. gitleaks-action v2.3.9 has no released Node.js 24 build (PR #215 upstream is in flight). Opt in now via the documented FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 env override to eliminate the deprecation warning today and ensure continued operation past the cutover. Drop the override once gitleaks-action publishes a node24-pinned release. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"to the gitleaks-action env block.Why
GitHub forces Node.js 20 actions onto Node.js 24 on 2026-06-02. gitleaks-action v2.3.9 has no Node.js 24 release (upstream PR #215 in flight). The documented escape hatch eliminates the deprecation warning now and protects against the upcoming cutover. Drop the override once an upstream node24-pinned release ships.
Test plan
Node.js 20 actions are deprecatedwarning gone from Security Scans output🤖 Generated with Claude Code