CI maintenance: 3 green fix PRs unmerged for 3 weeks — action needed

[erudenko]

Current CI status (as of 2026-05-05)

This is an automated maintenance report. No new code changes are required — the fixes already exist as open PRs. Action needed is human review and merge.

---

Failing runs

Run ID	Workflow	PR	Status	Root cause
24298790072	Test Plugins	#32	❌ failure	TS type errors on base branch (fix only broadened triggers, not code)
24298790076	Test Stats Plugin	#32	❌ failure	Stale dates on base branch
24298782547	Test Stats Plugin	#32	❌ failure	Stale dates on base branch

PR #31 and PR #28 only triggered GitGuardian — test CI never ran on them due to the now-fixed branch-filter bug.

---

What's already fixed

All root causes from the failing runs above were fixed weeks ago in multiple green PRs:

PR	Branch	All checks	Fixes
#24	fix/ci-24065489776-ts-and-dates	✅ 7/7	TS unused imports, rolling stats dates, browser-use 1.1.2, CI trigger for fix branch
#33	fix/ci-consolidated	✅ 7/7	Everything in #24 + fully unrestricted CI triggers (no branch allowlist)
#34	fix/ci-all-fixes-final	✅ 13/13	Everything in #24 + rolling dates in integration.test.ts + browser-use 1.1.2

All three have been green since 2026-04-12 and have not been merged.

---

Superseded / stale PRs

These PRs can be closed — their fixes are fully covered by the green PRs above:

PR	Branch	Why superseded
#22	fix/ci-typescript-and-stats-dates	Subset of #24; CI never ran (branch-filter bug)
#23	fix/ci-typescript-and-stats-dates-resolved	Subset of #24; CI never ran
#28	fix/ci-24276607217-browser-use-version	browser-use fix already in #24, #33, #34
#31	fix/ci-main-browser-use-version	Targets main (dist-only orphan), CI cannot run there
#32	fix/ci-workflow-trigger-broadening	Trigger fix only; superseded by #33 which also fixes code

---

Recommended action

1. Merge 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) — most comprehensive, 13/13 checks green. It is based on fix/ci-type-errors-and-stale-test-date, the source code branch.
   • If fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 is preferred as a smaller, focused PR, merge that first; then fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34's diff shrinks to just two files.
2. Close PRs fix(ci): remove unused TS imports + fix stale stats test dates #22, fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23, fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28, fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31, fix(ci): remove hardcoded branch filters from workflow triggers #32 as superseded (reference this issue in the close message).
3. Consider whether fix/ci-type-errors-and-stale-test-date should be merged or rebased onto main's source history at some point — the current branch topology has source code on a fix/* branch rather than a conventional develop/main branch.

---

Automated CI maintenance report — no code changes made in this issue.

[erudenko]

CI maintenance status update — 2026-05-06

No change since yesterday's report. The failing runs (24298790072, 24298790076, 24298782547) on PR #32 remain the only active failures, and no new CI failures have appeared on any branch.

Corrected merge recommendation (updated from issue body):

PR	Branch	CI	Mergeable	Verdict
#34	fix/ci-all-fixes-final	✅ 13/13 green	✅ clean	Merge this one
#33	fix/ci-consolidated	✅ 7/7 green	❌ dirty (conflict)	Cannot merge without rebase
#24	fix/ci-24065489776-ts-and-dates	✅ 7/7 green	N/A	Subset of #34

PR #34 is the correct merge target, not #33. PR #33 has developed a merge conflict since the issue was filed — it can be merged only after a rebase. PR #34 merges cleanly and covers the same ground.

---

Agent spam note: Issues #123–#131 (created May 3–5) are all duplicates of this one. Each automated maintenance agent run has been creating a new issue instead of updating the existing one, resulting in 10 near-identical issues in 3 days. Recommend closing #123–#131 as duplicates of this issue to reduce tracker noise.

---

Generated by Claude Code