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
Automated triage of the 10 most-recent failed GitHub Actions runs. The gh CLI and workflow-run API endpoints (logs, rerun) require authentication and are unavailable in this environment, so this issue captures findings and recommended actions.
Summary of Failed Runs
Run ID
Workflow
Branch
Root Cause
24276607217
Test Plugins
fix/ci-24065489776-ts-and-dates
browser-use version drift (1.1.1 vs 1.1.2) — fixed in PR #24 latest push; all checks now green
24276583408
Test Stats Plugin
fix/ci-type-errors-and-stale-test-date
Stale hardcoded date 2026-03-26 outside 7/14-day window
2. Stale hardcoded test dates (affects test-stats.yml / unit+integration tests)
plugins/stats/tests/db.test.ts and integration.test.ts used the hardcoded date "2026-03-26" which has since drifted outside the 7/14-day rolling query windows used by getSessionSummary, getTopTools, and getDurationTrend.
3. browser-use version drift in marketplace.json
plugins/browser-use/plugin.json was bumped to v1.1.2 but .claude-plugin/marketplace.json still had v1.1.1. The marketplace-sync integration test catches exactly this drift.
4. Structural: main is a dist-only orphan branch
main contains only 4070f70 dist: publish magus v7.3.0 (16 plugins) — no source, no tests, no .github/ directory. All CI runs on main will fail by definition. The source branch is fix/ci-type-errors-and-stale-test-date.
Current Fix Status
All three root-cause bugs are already fixed in PR #24 (fix/ci-24065489776-ts-and-dates → fix/ci-type-errors-and-stale-test-date):
✅ Removes 3 unused TS imports
✅ Replaces stale hardcoded dates with dynamic TODAY/YESTERDAY/TWO_DAYS_AGO
✅ Bumps browser-use version in marketplace.json to 1.1.2
✅ Re-enables CI triggers on fix/ci-type-errors-and-stale-test-date
✅ Latest CI run (24278705651, 2026-04-11T08:33): all 7 checks green
Address the main branch structure — the CI workflow files (test-plugins.yml, test-stats.yml) trigger on branches: [main]. Since main is dist-only, those runs will always fail. Consider either:
Updating the branch trigger to the real source branch, OR
Documenting that main CI failures are expected/ignored (noisy false-positives)
What This Agent Cannot Do (Constraints)
No gh CLI available → cannot gh run rerun the failed runs
GitHub Actions REST API requires authentication for log downloads → cannot fetch raw failure logs
No workflow-run MCP tools → cannot list/view/rerun via API calls
Did not create new fix branches (all root causes already covered by existing PRs)
CI Maintenance Triage — 2026-04-11
Automated triage of the 10 most-recent failed GitHub Actions runs. The
ghCLI and workflow-run API endpoints (logs, rerun) require authentication and are unavailable in this environment, so this issue captures findings and recommended actions.Summary of Failed Runs
fix/ci-24065489776-ts-and-datesfix/ci-type-errors-and-stale-test-date2026-03-26outside 7/14-day windowfix/ci-type-errors-and-stale-test-dateexistsSync,vi,removeGitignoreEntries)mainmainis dist-only orphan, no source codemainfix/ci-type-errors-and-stale-test-datePRfix/ci-type-errors-and-stale-test-datePRmainmainmainRoot Causes
1. TS6133 unused imports (affects
test-plugins.yml/Run type checkstep)Three imports left behind after refactors cause
tsc --noEmitto fail undernoUnusedLocals:tools/claudeup-core/src/__tests__/integration/conventions-integration.test.ts:removeGitignoreEntriestools/claudeup-core/src/__tests__/unit/doctor.test.ts:vitools/claudeup-core/src/services/conventions-manager.ts:existsSync2. Stale hardcoded test dates (affects
test-stats.yml/ unit+integration tests)plugins/stats/tests/db.test.tsandintegration.test.tsused the hardcoded date"2026-03-26"which has since drifted outside the 7/14-day rolling query windows used bygetSessionSummary,getTopTools, andgetDurationTrend.3.
browser-useversion drift inmarketplace.jsonplugins/browser-use/plugin.jsonwas bumped tov1.1.2but.claude-plugin/marketplace.jsonstill hadv1.1.1. Themarketplace-syncintegration test catches exactly this drift.4. Structural:
mainis a dist-only orphan branchmaincontains only4070f70 dist: publish magus v7.3.0 (16 plugins)— no source, no tests, no.github/directory. All CI runs onmainwill fail by definition. The source branch isfix/ci-type-errors-and-stale-test-date.Current Fix Status
All three root-cause bugs are already fixed in PR #24 (
fix/ci-24065489776-ts-and-dates→fix/ci-type-errors-and-stale-test-date):TODAY/YESTERDAY/TWO_DAYS_AGObrowser-useversion inmarketplace.jsonto1.1.2fix/ci-type-errors-and-stale-test-dateRecommended Actions
Merge PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 — all checks passing, all root causes addressed. This will restore green CI on the
fix/ci-type-errors-and-stale-test-datesource branch.Close PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28 (
fix/ci-24276607217-browser-use-version) — the browser-use version fix it proposes is already included in PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24's latest commit. PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28 only has a GitGuardian check (the test workflows never ran on it), so it's safe to close as superseded.Close PRs fix(ci): remove unused TS imports + fix stale stats test dates #22 and fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23 — both are earlier attempts at the same fixes (TS imports + stale dates), now fully superseded by the more comprehensive PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24.
Address the
mainbranch structure — the CI workflow files (test-plugins.yml,test-stats.yml) trigger onbranches: [main]. Sincemainis dist-only, those runs will always fail. Consider either:mainCI failures are expected/ignored (noisy false-positives)What This Agent Cannot Do (Constraints)
ghCLI available → cannotgh run rerunthe failed runs