chore(deps): update gitleaks/gitleaks-action action to v3#192
Merged
Conversation
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
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.
This PR contains the following updates:
v2→v3Release Notes
gitleaks/gitleaks-action (gitleaks/gitleaks-action)
v3.0.0Compare Source
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@v2togitleaks/gitleaks-action@v3.Migration
Why
GitHub is deprecating the Node 20 runtime for Actions:
gitleaks-action@v2(Node 20) will still run, but only ifACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=trueis set as an environment variable.gitleaks-action@v2stops working regardless of any opt-out flag.Changes
action.yml: runtimenode20→node24@actions/core: 1.10.0 → 1.11.1dist/rebuiltactions/checkout@v6andgitleaks-action@v3Self-hosted runners
If you use self-hosted runners, ensure your runner version is
>= v2.327.1(required for Node 24 support).v3Compare Source
v2.3.9Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2.3.8...v2.3.9
v2.3.8Compare Source
What's Changed
New Contributors
Full Changelog: gitleaks/gitleaks-action@v2.3.7...v2.3.8
v2.3.7Compare Source
What's Changed
New Contributors
Full Changelog: gitleaks/gitleaks-action@v2.3.6...v2.3.7
v2.3.6Compare Source
What's Changed
New Contributors
Full Changelog: gitleaks/gitleaks-action@v2...v2.3.6
v2.3.5Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2...v2.3.5
v2.3.4Compare Source
Full Changelog: gitleaks/gitleaks-action@v2.3.3...v2.3.4
v2.3.3Compare Source
What's Changed
GITLEAKS_VERSIONenv var by @spaze in #123New Contributors
Full Changelog: gitleaks/gitleaks-action@v2.3.2...v2.3.3
v2.3.2Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2.3.1...v2.3.2
v2.3.1Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2.3.0...v2.3.1
v2.3.0Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2...v2.3.0
v2.2.1Compare Source
What's Changed
Full Changelog: gitleaks/gitleaks-action@v2...v2.2.1
v2.2.0Compare Source
What's Changed
You can now run scheduled runs with gitleaks-action. A scheduled gitleaks-action will scan the entire history of a repo. You can set up a scheduled run by adding
scheduleto theonentry:Full Changelog: gitleaks/gitleaks-action@v2...v2.2.0
v2.1.4Compare Source
What's Changed
v2.1.3Compare Source
What's New
v2.1.2Compare Source
v2.1.1Compare Source
What's New
v2.1.0Compare Source
What's new
v2.0.8Compare Source
What's New
v2.0.7Compare Source
What's Changed:
v2.0.6Compare Source
What's New:
v2.0.5Compare Source
What's New
baseandheadrefs are the same.v2.0.4Compare Source
What's New
v2.0.3Compare Source
What's New
eventJson.commitsfor commit range rather thaneventJson.beforeandeventJson.after. This fixesinvalid revision rangeon push event errors.v2.0.2Compare Source
What's New
nameso this action can be published on the marketplacev2.0.1Compare Source
What's New
GITLEAKS_ENABLE_SUMMARYenv var option to enable or disable Gitleaks-action job summaries (defaults to true)GITLEAKS_ENABLE_UPLOAD_ARTIFACTenv var option to enable or disable Gitleaks-action job artifact uploads (defaults to true)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.