Update pre-commit hook gitleaks/gitleaks to v8.28.0 #3643
Merged
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:
v8.27.2
->v8.28.0
Note: The
pre-commit
manager in Renovate is not supported by thepre-commit
maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
gitleaks/gitleaks (gitleaks/gitleaks)
v8.28.0
Compare Source
Changelog
4fb4382
cant countb1c9c7e
Composite rules (#1905)72977e4
feat: add Anthropic API key detection (#1910)7b02c98
fix(git): handle port (#1912)2a7bcff
dont prematurely calculate fragment newlines (#1909)bd79c3e
feat(allowlist): promote optimizations (#1908)7fb4eda
Fix: CVEs on go and go crypto (#1868)a044b81
feat: add artifactory reference token and api key detection (#1906)bf380d4
sillyf487f85
Update gitleaks.yml958f55a
add just like that, no leaksOptimizations
#1909 waits to find newlines until a match. This ends up saving a boat load of time since before we were finding newlines for every fragment regardless if a rule matched or not.
#1908 promoted @rgmz excellent stopword optimization
Composite Rules (Multi-part or
required
Rules) #1905In v8.28.0 Gitleaks introduced composite rules, which are made up of a single "primary" rule and one or more auxiliary or
required
rules. To create a composite rule, add a[[rules.required]]
table to the primary rule specifying anid
and optionallywithinLines
and/orwithinColumns
proximity constraints. A fragment is a chunk of content that Gitleaks processes at once (typically a file, part of a file, or git diff), and proximity matching instructs the primary rule to only report a finding if the auxiliaryrequired
rules also find matches within the specified area of the fragment.Proximity matching: Using the
withinLines
andwithinColumns
fields instructs the primary rule to only report a finding if the auxiliaryrequired
rules also find matches within the specified proximity. You can set:withinLines: N
- required findings must be within N lines (vertically)withinColumns: N
- required findings must be within N characters (horizontally)Here are diagrams illustrating each proximity behavior:
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.