chore(security): re-pin the one fingerprint the history rewrite moved - #169
Merged
Merged
Conversation
Purging .env.bak-2026-07-28 rewrote every commit from 2026-07-28 onward, so any gitleaks fingerprint pinned to one of those commits stopped resolving. Only one was affected: a later commit also carries the pk_test_ fixture line, and it came out of the rewrite with a new SHA. Commits before the purge point kept their SHAs, so the existing four entries still resolve and are left alone. Full history now scans clean — `gitleaks detect --source .` exits 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
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.
Follow-up to the history scrub.
masterwente3d0f63→5a51ce2when.env.bak-2026-07-28was purged withgit filter-repo.A gitleaks fingerprint pins a commit SHA, and the rewrite changed the SHA of every commit from 2026-07-28 onward. Commits before that point kept their SHAs, so the four existing entries still resolve and are untouched. One later commit also carries the
pk_test_fixture line and came out of the rewrite with a new SHA — that's the single entry added here.Verification:
gitleaks detect --source .over full history now reportsno leaks found, exit 0. Before this commit it reported 1.Nothing real is suppressed. The 21 credentials are gone from every commit rather than hidden —
git log --all -- .env.bak-2026-07-28returns nothing, a fresh clone from GitHub has 0 references, and GitHub refuses to serve the old commit (upload-pack: not our ref).🤖 Generated with Claude Code