CI Failure Audit (2026-05-04)
This issue documents the result of a CI maintenance scan of recently failed GitHub Actions runs. No gh CLI was available, so the analysis was performed via the GitHub API (PR check runs).
Failed runs found
Run ID
Job
Workflow
PR
Conclusion
Root cause
24298790072
test (20)
Test Plugins
#32
FAILURE
TS unused imports + stale dates inherited from base branch
24298790076
test
Test Stats Plugin
#32
FAILURE
Stale hardcoded dates in stats tests
24298782547
test
Test Stats Plugin
#32
FAILURE
Stale hardcoded dates in stats tests
All three failures are in PR #32 (fix/ci-workflow-trigger-broadening). That PR only changed the workflow YAML trigger filters, but its base branch (fix/ci-type-errors-and-stale-test-date) still contained the unresolved bugs (TS6133 unused imports, stale 2026-03-26 date in stats tests). So CI ran for the first time on that branch and hit both bugs.
These failures are not transient — they have concrete root causes that are already fixed elsewhere.
Root causes (all already fixed)
#
Root cause
Fixed in
1
tsc --noEmit fails: unused imports removeGitignoreEntries, vi, existsSync
PRs #22 , #23 , #24 , #33
2
Stats tests use hardcoded 2026-03-26 — outside 7/14-day rolling query windows
PRs #22 , #23 , #24 , #33 , #34
3
browser-use version 1.1.1 in marketplace.json vs 1.1.2 in plugin.json
PRs #28 , #31 , #33 , #34
4
Workflow triggers had hardcoded branches allowlist — CI silently skipped new branches
PRs #32 , #33
Current PR CI status
PR
Branch
All checks green?
Notes
#24
fix/ci-24065489776-ts-and-dates
✅ Yes (7/7)
Code fixes only; partial trigger fix
#33
fix/ci-consolidated
✅ Yes (7/7)
Comprehensive: code + trigger broadening
#34
fix/ci-all-fixes-final
✅ Yes (13/13)
Adds integration.test.ts date fix on top of #33
#32
fix/ci-workflow-trigger-broadening
❌ 3 failures
Superseded by #33
#31
fix/ci-main-browser-use-version
⚠️ GitGuardian only
Targets dist-only main — test CI structurally cannot run there
#28
fix/ci-24276607217-browser-use-version
⚠️ GitGuardian only
Branch not in old trigger allowlist; superseded by #33
#22
fix/ci-typescript-and-stats-dates
⚠️ GitGuardian only
Same trigger issue; superseded by #24
#23
fix/ci-typescript-and-stats-dates-resolved
⚠️ GitGuardian only
Same trigger issue; superseded by #24
Recommended actions
Merge (in order)
Merge PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (fix/ci-consolidated → fix/ci-type-errors-and-stale-test-date).
This is the single most complete fix: removes unused TS imports, fixes stale dates, bumps browser-use to 1.1.2, and removes the hardcoded branch trigger filters. All 7 checks are green.
(If PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 is merged first, PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 's diff will shrink to just the two workflow-YAML changes.)
Evaluate PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 (fix/ci-all-fixes-final). After fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 merges, review whether the additional integration.test.ts date fixes it adds are still needed (they may already be included via fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 's head).
Close as superseded / not-planned
PR fix(ci): remove hardcoded branch filters from workflow triggers #32 — same trigger fix as fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 , but without the code fixes; all failures are addressed by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 .
PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31 — targets dist-only main; test workflows don't exist on that branch; browser-use fix is covered by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 .
PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28 — browser-use version fix only; covered by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 .
PR fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23 — superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 .
PR fix(ci): remove unused TS imports + fix stale stats test dates #22 — superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 .
No new fix branch needed
All identified failures are non-transient and are already resolved in at least one green PR. The only required action is merging the existing fix PRs in the order above and closing the stale ones.
Automated CI audit by Claude Code — https://claude.ai/code/session_012MCJwa9nsRHTHkUELXtekP
CI Failure Audit (2026-05-04)
This issue documents the result of a CI maintenance scan of recently failed GitHub Actions runs. No
ghCLI was available, so the analysis was performed via the GitHub API (PR check runs).Failed runs found
test (20)testtestAll three failures are in PR #32 (
fix/ci-workflow-trigger-broadening). That PR only changed the workflow YAML trigger filters, but its base branch (fix/ci-type-errors-and-stale-test-date) still contained the unresolved bugs (TS6133 unused imports, stale2026-03-26date in stats tests). So CI ran for the first time on that branch and hit both bugs.These failures are not transient — they have concrete root causes that are already fixed elsewhere.
Root causes (all already fixed)
tsc --noEmitfails: unused importsremoveGitignoreEntries,vi,existsSync2026-03-26— outside 7/14-day rolling query windowsbrowser-useversion1.1.1inmarketplace.jsonvs1.1.2inplugin.jsonbranchesallowlist — CI silently skipped new branchesCurrent PR CI status
fix/ci-24065489776-ts-and-datesfix/ci-consolidatedfix/ci-all-fixes-finalintegration.test.tsdate fix on top of #33fix/ci-workflow-trigger-broadeningfix/ci-main-browser-use-versionmain— test CI structurally cannot run therefix/ci-24276607217-browser-use-versionfix/ci-typescript-and-stats-datesfix/ci-typescript-and-stats-dates-resolvedRecommended actions
Merge (in order)
Merge PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (
fix/ci-consolidated→fix/ci-type-errors-and-stale-test-date).This is the single most complete fix: removes unused TS imports, fixes stale dates, bumps
browser-useto1.1.2, and removes the hardcoded branch trigger filters. All 7 checks are green.(If PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 is merged first, PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33's diff will shrink to just the two workflow-YAML changes.)
Evaluate PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 (
fix/ci-all-fixes-final). After fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 merges, review whether the additionalintegration.test.tsdate fixes it adds are still needed (they may already be included via fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33's head).Close as superseded / not-planned
main; test workflows don't exist on that branch; browser-use fix is covered by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33.No new fix branch needed
All identified failures are non-transient and are already resolved in at least one green PR. The only required action is merging the existing fix PRs in the order above and closing the stale ones.
Automated CI audit by Claude Code — https://claude.ai/code/session_012MCJwa9nsRHTHkUELXtekP