You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test: use an obviously-fake Google API key fixture #7
Replace the Google API key literal used as a test fixture in packages/http-recorder/test/record-replay.test.ts with an obviously-fake
value so it stops tripping secret scanners.
Why
The old literal (AIzaSyDHibiBRvJZLsFnPYPoiTwxY4ztQ55yqCE) matched the Google
API key detector format closely enough to raise false positives, even though it
was never a real credential. The new value (AIzaSyFakeTestKeyForSecretDetectionOnly0001)
still satisfies the detector regex AIza[0-9A-Za-z_-]{20,}, so the existing secretFindings assertion (expects reason "Google API key") stays valid.
Scope
One test fixture literal changed; no production code touched.
Acceptance
The secretFindings assertion in record-replay.test.ts still passes (reason
"Google API key") and the literal no longer resembles a live key.
Activity