March 11, 20261.0.113v1.0.113RSS

v1.0.113 — feat: Multi-Product Fleet Control Room Dashboard

Release v1.0.113: Blocked — Fleet Control Room Dashboard Did Not Merge

Date: 2026-03-11

What happened

This release tag was created for PR #126 (Multi-Product Fleet Control Room Dashboard), but the merge was blocked and no new code shipped.

  • The CI Test job failed on all 5 consecutive runs against the feat/fleet-dashboard branch
  • npx vitest run exits non-zero; the exact failing tests need local investigation
  • The PR modifies several test files and vitest.config.ts to handle Vitest 3.x unhandled rejection behavior — those changes did not resolve the failures

What needs to happen

  1. Run npx vitest run locally to identify the specific failing tests
  2. Fix the failures and push a new commit
  3. Confirm a green CI run before re-requesting a merge

Technical notes

No database changes, no new routes, and no user-facing changes landed. The fleet router and dashboard component (src/lib/routers/fleet.ts, src/components/fleet-dashboard-content.tsx) remain unmerged.

Release Notes

I've done a thorough investigation. The CI is consistently failing (5 consecutive runs) on the Test job. The test output log is being cut off before revealing the exact failing test names. Given that:

  1. The PR's mergeable field is false
  2. All 5 recent CI runs on the branch have conclusion: "failure"
  3. The merge attempt was rejected with "CI checks failed: Test"
  4. This is a consistent, reproducible failure — not a transient flake

I must stop and report the failure rather than proceeding with the merge. PR #126 cannot be merged in its current state due to failing CI tests.

❌ Merge Blocked — CI Tests Failing

PR #126 cannot be merged. The merge was rejected because the CI Test job is consistently failing across all 5 recent CI runs on the feat/fleet-dashboard branch.

What I found

CheckStatus
CI Run #22941693101❌ failure
CI Run #22941617504❌ failure
CI Run #22941516956❌ failure
CI Run #22941480940❌ failure
CI Run #22941409285❌ failure

The Failure

  • Failing step: Run tests (the test job in ci.yml)
  • The test runner (npx vitest run) is exiting with a non-zero code
  • The raw CI log excerpt confirms the failure is in the test suite, not the build or typecheck steps

What the PR touches (test-related)

The PR modifies several test files to work around Vitest 3.x unhandled rejection behavior:

  • tests/inngest/deal-staleness-escalation-cron.test.ts
  • tests/inngest/pipeline-failure-autofix.test.ts
  • tests/lib/agent-logger.test.ts
  • tests/lib/data-export-fulfillment-cron.test.ts
  • tests/lib/stale-pipeline-recovery-cron.test.ts
  • tests/lib/routers/fleet.test.ts (new)
  • vitest.config.ts — adds dangerouslyIgnoreUnhandledErrors: true

What needs to happen before this can merge

  1. The PR author needs to identify the specific test(s) failing (run npx vitest run locally to see the full output)
  2. Fix the failing test(s) and push a new commit
  3. Confirm CI passes with a green ✅ run before re-requesting a merge

Once CI is green, the merge, tag v1.0.113, and release can proceed immediately.