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
fix(guardrails): test-windows-secrets fails on main on the allowed-roots link case #10276
Every pull request's test-windows-secrets run inherits this failure (seen on #10120), so the job is red on PRs that do not touch guardrails.
Likely cause (UNVERIFIED)
Guardrails commits in 7f2457b..2640984: #9981 (deny recursive deletes of protected trees ahead of the allowed roots) is the closest match to an "allowed roots" case; #10019 (exempt local-only paths from secret-pattern-detection) also touches this hook. Windows-only; not reproducible on Linux.
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: the Windows secrets test job fails on main with one case ("allowed roots: through a link outside D that lands under D", expected exit 0, got 2). The failure appeared between the last passing run and the two failing runs, and it carries into every PR's run. The suspected cause is a recent guardrails change (#9981 or #10019), and nobody has verified it. The fix is to find the regression, using the Windows run logs and the commit range, and make the job pass again. I found no likely duplicates among the open issues.
The work-resolve-issue lane stopped partway through this issue and needs a person.
Why, in the run's own words:
Nothing to change. The failing case is already fixed on main by 300e58f (#10280, 2026-10-26, "fix(guardrails): resolve only the existing ancestor through cygpath for an allowed-roots link"). test-windows-secrets has passed on every scheduled main run since b59666b (runs 40360157201, 40481545922, 40540682796, 40663903199, 40725629371). This run made no change. The issue's done-when item is already met, so a person should close the issue as resolved by #10280.
What the run says it did not do:
This run did not execute secret-pattern-detection.test.sh: the test is Windows-only and this lane cannot run it. Evidence that it passes comes from main's scheduled pr-test-windows runs.
Tidy, review, build/test and class-audit steps were skipped because there is no diff.
The issue was not closed: this lane cannot close issues. It needs a person to close it as resolved by #10280.
Re-triage: closing. The only done-when item, "test-windows-secrets passes on main", is met.
The fix is #10280 (merge 300e58f5a6, 2026-10-26, "fix(guardrails): resolve only the existing ancestor through cygpath for an allowed-roots link"), which fixes the failing allowed-roots link case.
Activity
github-actions commentedon Oct 26, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: the Windows secrets test job fails on main with one case ("allowed roots: through a link outside D that lands under D", expected exit 0, got 2). The failure appeared between the last passing run and the two failing runs, and it carries into every PR's run. The suspected cause is a recent guardrails change (#9981 or #10019), and nobody has verified it. The fix is to find the regression, using the Windows run logs and the commit range, and make the job pass again. I found no likely duplicates among the open issues.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 29, 2026
The work-resolve-issue lane stopped partway through this issue and needs a person.
Why, in the run's own words:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40790265869
To retry, remove
needs-humanand addagent-readyagain.kyle-sexton commentedon Oct 29, 2026
Re-triage: closing. The only done-when item, "test-windows-secrets passes on main", is met.
test-windows-secretsconcludedsuccess.needs-humanis on this issue only because the lane cannot close issues. It is not an intent or security hold.