docs(notes): track gitleaks Node24 override removal followup#230
Merged
docs(notes): track gitleaks Node24 override removal followup#230
Conversation
On 2026-05-06 we set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true on every gitleaks-action invocation across the ecosystem (6 repos) to silence the Node.js 20 deprecation warning ahead of GitHub's 2026-06-02 forced-migration. The override is temporary — must be removed once gitleaks-action publishes a release that runs on Node.js 24 natively. This notes file documents: - Why the override exists - Detection signals (upstream PR #215 / #207 merge, action.yml runs.using) - The removal procedure (one-line edit per repo, six repos) - Locator command for finding the override line - Tripwires for the 2026-06-02 cutover Tracked in juniper-ml#229. 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
Adds `notes/FOLLOWUP_GITLEAKS_NODE24_OVERRIDE.md` documenting the open obligation to remove `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24` from every gitleaks-action invocation once upstream ships a node24-pinned release.
Why
The 2026-05-06 ecosystem-wide override (6 repos) was a temporary measure. Without an in-tree tripwire it could outlive its purpose. The notes file documents:
Companion artifacts:
Test plan
🤖 Generated with Claude Code