Repository navigation
chore(secrets): refresh .secrets.baseline line-number drift - #3700
PetrefiedThunder wants to merge 1 commit into
Conversation
…rity workflow on main)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review.
|
PR Blocker ChecklistHead SHA: Status: Ready
|
|
Duplicate of #3703, closed per VS Code Lead; branch kept |
The security workflow's Secrets Audit step fails on main (exit 3: "The baseline file was updated") because baseline line numbers drifted; no new findings. Refreshed with detect-secrets 1.5.0 using the exact security.yml command (generated by Codex in a fresh temp clone, verified independently). Diff: 6 line_number values + generated_at only; all 452 entries unchanged.
Infra sweep 2026-10-28 ~4 AM PT.
Note
Low Risk
Metadata-only baseline refresh with no new or removed secret findings; no runtime or application code changes.
Overview
Updates
.secrets.baselineso the Secrets Audit step stops failing with “baseline file was updated” after unrelated edits shifted line numbers in a handful of test files. The refresh was done with detect-secrets 1.5.0, matching CI/pre-commit.Only six existing entries had their
line_numbermetadata adjusted (frontend session-origin, api-security JWT fixture, graph labels security test);hashed_secretvalues and the rest of the baseline are unchanged.generated_atwas bumped to the new scan time.Reviewed by Cursor Bugbot for commit 055b12f. Bugbot is set up for automated code reviews on this repo. Configure here.