Harden dependency floors and update the Vitest toolchain to patched releases. - upgrade workspace vitest and @vitest/coverage-v8 dependencies to the 4.1 line across packages and plugins - pin transitive protobufjs via pnpm overrides and lockfile updates to patched versions - adapt Vitest configs, engine test helpers, and security-floor coverage for the new dependency baselines - add the published CLI changeset and related workspace/package metadata updates included in the task branch Files changed: .changeset/fn-6042-security-dependencies.md | 5 + AGENTS.md | 4 + Dockerfile | 3 + docs/PLUGIN_AUTHORING.md | 2 - package.json | 3 +- packages/cli/package.json | 4 +- packages/cli/vitest.config.ts | 2 +- packages/core/package.json | 4 +- packages/core/vitest.config.ts | 2 +- packages/dashboard/app/test/mockApi.ts | 4 +- packages/dashboard/package.json | 4 +- packages/dashboard/vitest.config.ts | 2 +- packages/desktop/package.json | 4 +- packages/desktop/vitest.config.ts | 2 +- packages/droid-cli/package.json | 2 +- packages/droid-cli/vitest.config.ts | 2 +- packages/engine/package.json | 4 +- .../engine/src/__tests__/executor-test-helpers.ts | 29 +- .../engine/src/__tests__/gridlock-detector.test.ts | 5 +- .../src/__tests__/heartbeat-scheduler.test.ts | 3 +- packages/engine/src/__tests__/scheduler.test.ts | 24 +- packages/engine/src/__tests__/self-healing.test.ts | 5 + packages/engine/tsconfig.json | 3 +- packages/engine/vitest.config.ts | 10 +- packages/i18n/package.json | 2 +- packages/i18n/vitest.config.ts | 7 + packages/mobile/package.json | 2 +- packages/mobile/vitest.config.ts | 2 +- packages/pi-claude-cli/package.json | 2 +- packages/pi-claude-cli/vitest.config.ts | 2 +- packages/pi-llama-cpp/package.json | 2 +- packages/pi-llama-cpp/vitest.config.ts | 2 +- packages/plugin-sdk/package.json | 2 +- packages/plugin-sdk/vitest.config.ts | 2 +- .../examples/fusion-plugin-auto-label/package.json | 2 +- .../fusion-plugin-auto-label/vitest.config.ts | 2 +- .../examples/fusion-plugin-ci-status/package.json | 2 +- .../fusion-plugin-ci-status/vitest.config.ts | 2 +- .../fusion-plugin-notification/package.json | 2 +- .../fusion-plugin-notification/vitest.config.ts | 2 +- .../fusion-plugin-settings-demo/package.json | 2 +- .../fusion-plugin-settings-demo/vitest.config.ts | 2 +- plugins/fusion-plugin-acp-runtime/package.json | 2 +- plugins/fusion-plugin-acp-runtime/vitest.config.ts | 2 +- plugins/fusion-plugin-agent-browser/package.json | 2 +- .../fusion-plugin-agent-browser/vitest.config.ts | 2 +- .../fusion-plugin-cli-printing-press/package.json | 2 +- .../vitest.config.ts | 2 +- .../package.json | 2 +- .../src/__tests__/orchestrator-live-output.test.ts | 4 +- .../vitest.config.ts | 2 +- plugins/fusion-plugin-cursor-runtime/package.json | 4 +- .../fusion-plugin-dependency-graph/package.json | 4 +- .../vitest.config.ts | 2 +- plugins/fusion-plugin-droid-runtime/package.json | 2 +- .../fusion-plugin-droid-runtime/vitest.config.ts | 2 +- plugins/fusion-plugin-even-cards/package.json | 2 +- plugins/fusion-plugin-even-cards/vitest.config.ts | 2 +- .../package.json | 2 +- .../vitest.config.ts | 2 +- plugins/fusion-plugin-hermes-runtime/package.json | 2 +- .../fusion-plugin-hermes-runtime/vitest.config.ts | 2 +- .../fusion-plugin-openclaw-runtime/package.json | 2 +- .../vitest.config.ts | 2 +- .../fusion-plugin-paperclip-runtime/package.json | 2 +- .../vitest.config.ts | 2 +- plugins/fusion-plugin-reports/package.json | 2 +- .../src/__tests__/review-panel.test.ts | 6 +- plugins/fusion-plugin-reports/vitest.config.ts | 2 +- plugins/fusion-plugin-roadmap/package.json | 2 +- plugins/fusion-plugin-roadmap/vitest.config.ts | 2 +- plugins/fusion-plugin-whatsapp-chat/package.json | 2 +- .../fusion-plugin-whatsapp-chat/vitest.config.ts | 2 +- pnpm-lock.yaml | 626 ++++++++------------- .../__tests__/dependency-security-floor.test.mjs | 95 ++++ 75 files changed, 475 insertions(+), 491 deletions(-) Fusion-Task-Id: FN-6042 Fusion-Task-Lineage: fff6a1cb-8937-435c-9a91-b7c7a59cc80e
CI Status Plugin
Polls CI status for branches and provides a custom API to query results. Useful for tracking the build status of feature branches created for Fusion tasks.
Features
- Branch Tracking: Automatically tracks branches when tasks move to in-progress
- Periodic Polling: Polls CI status at configurable intervals
- Custom API: Provides REST endpoints to query branch status
- Automatic Cleanup: Stops tracking branches when tasks are completed
Installation
Option 1: Copy to plugins directory
cp -r fusion-plugin-ci-status ~/.fusion/plugins/
Option 2: Install via CLI
fn plugin install /path/to/fusion-plugin-ci-status
Configuration
Settings Reference
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
ciUrl |
string | Yes | — | Base URL for CI API |
pollIntervalMs |
number | No | 30000 |
How often to poll CI status (milliseconds) |
branchPrefix |
string | No | fusion/ |
Only poll branches with this prefix |
API Endpoints
The plugin provides the following REST endpoints at /api/plugins/fusion-plugin-ci-status:
GET /status
Returns status of all tracked branches.
{
"branches": [
{
"branch": "fusion/fn-001",
"status": "pending",
"lastChecked": "2024-01-01T00:00:00.000Z",
"url": "https://ci.example.com/builds/123"
}
]
}
GET /status/:branch
Returns status of a specific branch.
{
"branch": "fusion/fn-001",
"status": "success",
"lastChecked": "2024-01-01T00:00:00.000Z",
"url": "https://ci.example.com/builds/123"
}
If the branch is not found, returns a 404 error.
POST /refresh
Triggers an immediate CI status refresh for all tracked branches.
{
"branches": [...],
"refreshed": true
}
How It Works
- Branch Creation: When a task moves to "in-progress", the plugin creates a branch name using the configured prefix (default:
fusion/) combined with the task ID (lowercased) - CI Polling: At the configured interval, the plugin polls the CI API to get status updates for all tracked branches
- CI Integration: The plugin sends a POST request to
{ciUrl}/statuswith the list of branch names - Branch Cleanup: When a task moves to "done" or "archived", the branch is removed from tracking
CI API Integration
The plugin expects your CI system to expose a /status endpoint that accepts:
{
"branches": ["fusion/fn-001", "fusion/fn-002"]
}
And returns:
{
"statuses": [
{
"branch": "fusion/fn-001",
"status": "success",
"url": "https://ci.example.com/builds/123"
}
]
}
Supported Status Values
pending— Initial state when branch is first trackedrunning— CI is buildingsuccess— CI passedfailed— CI failedcancelled— CI was cancelled
Development
# Install dependencies
pnpm install
# Run tests
pnpm test
# Build
pnpm build
License
MIT