Skip to content

chore(security): re-pin the one fingerprint the history rewrite moved #169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralyodio merged 1 commit into from
Jul 30, 2026
Merged

chore(security): re-pin the one fingerprint the history rewrite moved #169

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .gitleaksignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,3 +24,9 @@
# 508859ed: the same curl example, by then reading `-H "Authorization: Bearer
# $SECRET"` — a shell variable the reader substitutes, not a token.
508859ed12ff73cd5044a4fd10971372779578cb:app/(marketing)/docs/autoblog-webhook/page.tsx:curl-auth-header:130

# Purging .env.bak-2026-07-28 from history (e3d0f63 -> 5a51ce2) rewrote every
# commit from 2026-07-28 onward; earlier commits kept their SHAs, so the four
# fingerprints above still resolve. What changed is the later commit that also
# carries the pk_test_ fixture line — it has a new SHA and needs its own entry.
b7360e66a22d02cf8c002ee9347240176b66dcea:tests/contract/tracker-integrations.test.ts:generic-api-key:8
Loading