Skip to content

ci: 4 fix PRs unmerged for 3+ weeks — recommended merge order and remaining risk #135

@erudenko

Description

@erudenko

CI Maintenance Audit — 2026-05-06

This issue was filed by the automated CI/CD maintenance agent after a full audit of recent check runs across all open PRs. No new CI failures have triggered since 2026-04-12 (no new pushes to any source branch), but four fix PRs from April are stalled unmerged and one latent failure risk remains in the base branch.


Current CI Status

PR Branch Last CI Result Superseded by
#24 fix/ci-24065489776-ts-and-dates 2026-04-11 ✅ All green #33
#28 fix/ci-24276607217-browser-use-version n/a (CI never fired) #24, #33
#31 fix/ci-main-browser-use-version n/a (targets dist-only main) N/A
#32 fix/ci-workflow-trigger-broadening 2026-04-12 test(20) failed, stats test failed #33
#33 fix/ci-consolidated 2026-04-12 ✅ All green (7/7 checks)
#34 fix/ci-all-fixes-final 2026-04-12 ✅ All green (13/13 checks)

Root Causes (all already fixed in PRs above)

Run ID Workflow Root Cause Fixed In
24065489776 Test Plugins tsc --noEmit — 3 unused TS imports (TS6133) PR #24, #33, #34
24063290384 Test Plugins same as above PR #24, #33, #34
24029941408 Test Stats Plugin hardcoded date 2026-03-26 in db.test.ts outside 7-day window PR #24, #33, #34
24029941414 Test Stats Plugin same as above PR #24, #33, #34
24276607217 Test Plugins browser-use version mismatch: plugin.json @ 1.1.2, marketplace.json @ 1.1.1 PR #24, #33, #34
24298790072 Test Plugins TS imports (inherited — PR #32 only fixed triggers, not code) PR #33, #34
24298790076 Test Stats Plugin stale dates in integration.test.ts (PR #32 didn't fix code) PR #33, #34

Structural issue (PRs #22, #23, #28, #31, #32 received no test CI): test-plugins.yml and test-stats.yml had a hardcoded branches allowlist [main, fix/ci-type-errors-and-stale-test-date]. Any other branch was invisible to CI. Fixed in PR #33 (triggers broadened — no branches key, path-filters only).


Recommended Merge Order

Merge PR #33 (fix/ci-consolidated) first. It is the single most complete fix:

  • Removes 3 unused TS imports (TS6133)
  • Replaces hardcoded dates with dynamic TODAY/YESTERDAY/TWO_DAYS_AGO in both db.test.ts and integration.test.ts
  • Bumps browser-use to 1.1.2 in marketplace.json
  • Removes hardcoded branches allowlist from both workflow files so all future fix/* branches get CI

After #33 merges, PRs #24, #28, #32, and #34 can be closed as superseded.


Remaining Risk (latent, not yet triggered)

The base branch fix/ci-type-errors-and-stale-test-date (SHA 7e440fb) only partially fixed the date problem:

  • plugins/stats/tests/db.test.ts — patched to use dynamic today (commit c8561cc)
  • plugins/stats/tests/integration.test.tsstill has hardcoded "2026-03-26" (41 days old as of today)

If any new commit is pushed directly to fix/ci-type-errors-and-stale-test-date before PR #33 is merged, CI will run and Test Stats Plugin will fail (getSessionSummary, getTopTools, getDurationTrend all return 0 rows against stale dates).

Resolution: merge PR #33. That commit (c480542) already contains the full integration.test.ts date fix.


PRs That Can Be Closed After #33 Merges


Filed by the CI/CD maintenance agent — no new code changes were made. Action required: human merge of PR #33.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingci

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions