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
The only open PR with current CI failures. Three jobs failed on 2026-04-12:
Job
Run ID
Conclusion
test (20)
24298790072
failure
test (Test Stats Plugin)
24298790076
failure
test (Test Stats Plugin)
24298782547
failure
Root cause: This PR only changed workflow YAML (removed hardcoded branch filters) but was stacked on fix/ci-type-errors-and-stale-test-date which still had broken TypeScript imports and stale hardcoded dates. The trigger fix worked — CI actually ran — but the tests themselves failed.
Status: Superseded entirely by PR #33 (which includes all code fixes + the trigger broadening).
Superseded by #33 (same trigger fix + all code fixes)
Stale Branches to Delete (~45 branches)
The repository has accumulated 45+ fix/ci-* branches from repeated CI maintenance runs. All of the failures they addressed are now covered by PR #33. These branches can be safely deleted after #33 is merged:
Consider adding branch protection rules or configuring the CI maintenance agent with a limit on open fix PRs to prevent future accumulation.
Why This Was Not Auto-Fixed
The CI failures on PR #32 are not transient (not network timeouts or rate limits). The code-level fixes already exist and are proven green in PR #33. Opening yet another fix PR would only add to the existing accumulation. Human review and merge is the correct resolution here.
CI Maintenance Report — 2026-05-03
This issue is filed by the automated CI maintenance agent after auditing all recent GitHub Actions failures and open fix PRs.
Active CI Failures
PR #32 (
fix/ci-workflow-trigger-broadening) — FAILING ❌The only open PR with current CI failures. Three jobs failed on 2026-04-12:
test (20)test(Test Stats Plugin)test(Test Stats Plugin)Root cause: This PR only changed workflow YAML (removed hardcoded branch filters) but was stacked on
fix/ci-type-errors-and-stale-test-datewhich still had broken TypeScript imports and stale hardcoded dates. The trigger fix worked — CI actually ran — but the tests themselves failed.Status: Superseded entirely by PR #33 (which includes all code fixes + the trigger broadening).
Currently Green Fix PRs (all checks pass ✅)
fix/ci-24065489776-ts-and-datesfix/ci-consolidatedfix/ci-all-fixes-finalPR #33 is the recommended merge target — it is the most comprehensive fix, covers all known failures, and all CI checks pass.
PRs to Close (superseded)
fix/ci-typescript-and-stats-datesfix/ci-typescript-and-stats-dates-resolvedfix/ci-24276607217-browser-use-versionfix/ci-main-browser-use-versionmainorphan (no source CI); superseded by #33fix/ci-workflow-trigger-broadeningStale Branches to Delete (~45 branches)
The repository has accumulated 45+
fix/ci-*branches from repeated CI maintenance runs. All of the failures they addressed are now covered by PR #33. These branches can be safely deleted after #33 is merged:Full list of stale fix/ci-* branches
fix/ci-23779059727fix/ci-23849758228-pnpm-workspacefix/ci-23849758228-standalonefix/ci-23849758228fix/ci-23971192917fix/ci-23979261331fix/ci-24022272585fix/ci-24029941408fix/ci-24063290384fix/ci-24065489776-marketplace-versionfix/ci-24065489776-pr-attemptfix/ci-24065489776-ts-and-dates(PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 — keep until merged or superseded)fix/ci-24065489776fix/ci-24276607217-browser-use-versionfix/ci-all-24065489776fix/ci-all-fixes-final(PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 — keep until merged or closed)fix/ci-all-typescript-errors-consolidatedfix/ci-consolidated(PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 — keep until merged)fix/ci-main-browser-use-versionfix/ci-pnpm-ignore-workspacefix/ci-pnpm-install-flagsfix/ci-pnpm-install-ignore-workspacefix/ci-pnpm-install-workspacefix/ci-pnpm-lockfile-skills-apifix/ci-pnpm-workspace-and-kanban-versionfix/ci-pnpm-workspace-claudeup-corefix/ci-pnpm-workspace-isolationfix/ci-pnpm-workspace-syncfix/ci-remaining-type-errorsfix/ci-remaining-type-errors-and-stats-datesfix/ci-test-plugins-ignore-workspacefix/ci-test-plugins-kanban-version-mismatchfix/ci-test-plugins-lockfilefix/ci-test-plugins-pnpm-flags-v2fix/ci-test-plugins-pnpm-ignore-workspacefix/ci-test-plugins-pnpm-installfix/ci-test-plugins-pnpm-install-flagsfix/ci-test-plugins-pnpm-v10fix/ci-test-plugins-pnpm-workspacefix/ci-test-plugins-workspace-isolationfix/ci-test-plugins-workspace-mismatchfix/ci-ts-errors-and-stale-dates-main-prfix/ci-ts-unused-imports-and-stale-datefix/ci-type-errors-and-stale-test-datefix/ci-typecheck-24065489776fix/ci-typecheck-and-stats-datesfix/ci-typescript-and-stats-datesfix/ci-typescript-and-stats-dates-resolvedfix/ci-unused-imports-typecheckfix/ci-workflow-trigger-broadeningci-maintenance-test-probeRecommended Actions (in order)
fix/ci-consolidated) — all 7 CI checks pass; this is the single PR that resolves every known failure.fix/ci-*branches listed above.Why This Was Not Auto-Fixed
The CI failures on PR #32 are not transient (not network timeouts or rate limits). The code-level fixes already exist and are proven green in PR #33. Opening yet another fix PR would only add to the existing accumulation. Human review and merge is the correct resolution here.