ci: PR backlog blocking landing of all CI fixes — action required to merge/close stale branches

[erudenko]

CI Maintenance Audit — 2026-05-06

This issue was created by the CI/CD maintenance agent after auditing recently failed GitHub Actions runs across all open PRs.

---

Failed Runs Found

The most recent CI failures visible are on PR #32 (fix/ci-workflow-trigger-broadening), from April 12, 2026:

Run ID	Workflow	Job	Result
24298790072	Test Plugins	test (20)	❌ failure
24298790072	Test Plugins	test (22)	⚠️ cancelled
24298790076	Test Stats Plugin	test	❌ failure
24298782547	Test Stats Plugin	test	❌ failure

---

Root Causes (already diagnosed)

1. Unused TypeScript imports (TS6133) — removeGitignoreEntries, vi, existsSync left behind after refactors; tsc --noEmit fails under noUnusedLocals.
2. Stale hardcoded test dates — plugins/stats/tests/db.test.ts and integration.test.ts used "2026-03-26", now outside the 7/14-day rolling query windows.
3. browser-use version mismatch — plugin.json = 1.1.2, marketplace.json = 1.1.1; caught by marketplace-sync integration test.
4. Hardcoded CI workflow branch allowlist — test-plugins.yml and test-stats.yml only triggered on main and fix/ci-type-errors-and-stale-test-date, making all other fix branches invisible to CI.

---

Current Status: All fixes are already implemented and green

PR	Branch	All CI Green?	Notes
#24	fix/ci-24065489776-ts-and-dates	✅ 7/7 checks pass	Comprehensive code fix (TS imports + dates + browser-use version + trigger broadening)
#33	fix/ci-consolidated	✅ 7/7 checks pass	Supersedes PR #32; based on #24's head
#34	fix/ci-all-fixes-final	✅ 13/13 checks pass	Additional integration.test.ts date fixes
#32	fix/ci-workflow-trigger-broadening	❌ failures (old)	Superseded by #33
#31	fix/ci-main-browser-use-version	⚠️ GitGuardian only	Targets dist-only main — test workflows don't exist there
#28	fix/ci-24276607217-browser-use-version	⚠️ GitGuardian only	Branch was in trigger allowlist blind spot
#23	fix/ci-typescript-and-stats-dates-resolved	⚠️ GitGuardian only	Superseded by #24
#22	fix/ci-typescript-and-stats-dates	⚠️ GitGuardian only	Superseded by #23 and #24

---

Recommended Action Plan

The fixes are done — what's needed is merging the right PRs and closing the stale ones.

Step 1 — Merge PR #24 or PR #33 (pick one)

Both are fully green. PR #33 (fix/ci-consolidated) is the most comprehensive single PR and is ready to merge. It includes:

• All TS import fixes
• All dynamic date fixes (db.test.ts + integration.test.ts)
• browser-use version bump
• Workflow trigger broadening (removes hardcoded branch allowlist)

If you prefer incremental merges: merge PR #24 first (all code fixes), then close #33 or rebase it.

Step 2 — Close stale/duplicate PRs

After merging #33 (or #24+#33), close these as superseded:

• PR fix(ci): remove unused TS imports + fix stale stats test dates #22 — superseded by fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23, fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24
• 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(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28 — superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 (browser-use fix included)
• 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; close as not applicable
• PR fix(ci): remove hardcoded branch filters from workflow triggers #32 — superseded by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33
• PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 — check if any of its fixes (integration.test.ts dynamic dates) are not already in fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33; if so, rebase and merge; otherwise close

Step 3 — Verify CI on the source branch after merge

After merging, confirm that the fix/ci-type-errors-and-stale-test-date branch (or whatever becomes the default source branch) runs clean CI on new pushes.

---

Why this issue rather than an automated fix

• The CI agent cannot run gh run rerun (no gh CLI in the environment)
• The failing runs are on a superseded branch — rerunning them would not reflect current code
• The code fixes are already implemented and green; the bottleneck is human PR review/merge decisions
• Deciding which PRs to merge vs. close in the correct order requires human judgment given the stacked/overlapping PR structure

cc @erudenko