ci(security): block Gitleaks findings introduced by pull requests #20
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/gitleaks-block-new-findings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rollout of root renderer change ai_projects#435 (owner decision D3), piloted on tke-directory#6/#7. Additive only: adds a blocking, redacted PR-range Gitleaks scan; the full-tree scan stays advisory. Pre-existing findings do not block.
Held: the security.yml change is additive only and the security job passes. CI fails at the pre-existing bun audit step (10 newly published advisories, 1 critical, e.g. proxy-addr via @modelcontextprotocol/sdk > express). The bun suite passes locally (272/272). Needs a dependency update before this can merge.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.