ci: 3 failed workflow runs on PR #32 — already superseded by PR #33 (action required: merge + close stale PRs)

[erudenko]

CI Maintenance Audit — 2026-04-14

This issue was created by the automated CI maintenance agent after auditing recently failed workflow runs.

---

Failed Runs Identified

Run ID	Workflow	Branch / PR	Failing Job	Root Cause
24298790072	Test Plugins	fix/ci-workflow-trigger-broadening (PR #32)	test (20)	TS6133: 3 unused imports → tsc --noEmit fails
24298790076	Test Stats Plugin	fix/ci-workflow-trigger-broadening (PR #32)	test	Stale hardcoded date 2026-03-26 outside 7/14-day query window
24298782547	Test Stats Plugin	push on same branch	test	Same stale date

Why these failed

PR #32 (fix/ci-workflow-trigger-broadening) only removes the hardcoded branches allowlist from workflow YAML files. It does not fix the underlying code issues in its base branch (fix/ci-type-errors-and-stale-test-date):

• 3 unused TypeScript imports flagged by noUnusedLocals
• Stale date 2026-03-26 in plugins/stats/tests/integration.test.ts — now 17+ days outside the 7-day and 14-day rolling query windows

---

Current PR Status (as of audit)

PR	Branch	CI	Covers
#24	fix/ci-24065489776-ts-and-dates	✅ All green	TS imports, stale dates, browser-use version, trigger expansion
#28	fix/ci-24276607217-browser-use-version	⚪ GitGuardian only (trigger blocked pre-#32)	browser-use version only
#31	fix/ci-main-browser-use-version	⚪ GitGuardian only (main is dist-only, no test workflows)	browser-use version on dist main
#32	fix/ci-workflow-trigger-broadening	❌ Failing	Trigger broadening only (missing code fixes in base)
#33	fix/ci-consolidated	✅ All green	TS imports + stale dates + browser-use version + trigger broadening
#34	fix/ci-all-fixes-final	✅ All green	Rolling dates in integration.test.ts + browser-use version

---

Analysis

No new fix branch is needed. The failures on PR #32 are already fully addressed by PR #33, which is a superset of #32 (includes all code-level fixes from #24 plus the trigger broadening). PR #33 CI is entirely green.

PR #34 also addresses the same issues and is green, but PR #33 already contains all of its changes.

Recommended action

1. Merge PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (fix/ci-consolidated) — this is the most comprehensive green PR. It fixes all known failures:

   • 3 unused TS imports
   • Stale dates in db.test.ts and integration.test.ts
   • browser-use version mismatch in marketplace.json
   • Hardcoded branch filters removed from both workflow YAML files

2. Close as superseded (after fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 merges):

   • 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 (trigger fix is included)
   • PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 — superseded by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (all fixes included)
   • 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 and fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (browser-use fix included)
   • PR 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 — superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 and fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (partial fixes)

3. Evaluate PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31 (fix/ci-main-browser-use-version → main) — targets the dist-only orphan main branch. No test CI runs there so it can't be verified automatically. Assess whether the dist branch needs this change independently of the source fix.

---

Why no automated fix was applied

The failures are not transient (not a network timeout or flaky test), and the fix is not a simple code change — it requires merging an existing PR (#33) and closing several stale PRs. These are repository management actions that require human judgment and authorization.

/cc @erudenko