Skip to content

fix(ci): suppress false positive gitleaks finding in secrets-scan#41

Merged
Pierozi merged 1 commit intomainfrom
fix/update
Apr 27, 2026
Merged

fix(ci): suppress false positive gitleaks finding in secrets-scan#41
Pierozi merged 1 commit intomainfrom
fix/update

Conversation

@Pierozi
Copy link
Copy Markdown
Contributor

@Pierozi Pierozi commented Apr 27, 2026

Summary

  • Gitleaks flags cargo-deny-0.18 (a cache key in a historical QA workflow commit) as a generic-api-key due to entropy — it is not a real secret
  • The offending commit (4d9a296) is reachable from main via tag history, so history rewriting is not viable; adding .gitleaksignore is the correct suppression mechanism
  • Pins the exact fingerprint so only this one finding is ignored, leaving future real leaks detectable

Test plan

  • Re-run the Security Scan / secrets-scan workflow manually via workflow_dispatch and confirm it passes

@Pierozi Pierozi merged commit 92e9ad1 into main Apr 27, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant