chore(release): v0.0.5

Version bump via changesets.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
gsxdsm
2026-04-22 21:26:23 -07:00
parent 41553a506b
commit d72153620b
5 changed files with 20 additions and 12 deletions

View File

@@ -1,5 +1,12 @@
# runfusion.ai
## 0.0.5
### Patch Changes
- Updated dependencies [41553a5]
- @runfusion/fusion@0.0.5
## 0.0.4
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "runfusion.ai",
"version": "0.0.4",
"version": "0.0.5",
"license": "MIT",
"description": "Launch Fusion with `npx runfusion.ai` — tiny alias for @runfusion/fusion.",
"homepage": "https://runfusion.ai",

View File

@@ -1,5 +1,16 @@
# @runfusion/fusion
## 0.0.5
### Patch Changes
- 41553a5: Harden agent lifecycle around closed tasks and heartbeat defaults.
- `HeartbeatMonitor.executeHeartbeat()` now exits before session creation when the resolved task is done/archived (reason `task_closed`) and clears the stale `agent.taskId` linkage so the guard isn't re-tripped on every tick.
- `HeartbeatTriggerScheduler.watchAssignments()` skips callback dispatch when the assigned task is already closed (when a `taskStore` is wired in).
- `POST /api/agents/:id/runs` performs the same preflight check and returns 409 with a structured error naming the task id + column, keeping the existing active-run 409 precedence.
- `AgentStore.createAgent()` now persists `runtimeConfig.heartbeatIntervalMs` (default 1h) on non-ephemeral agents so the dashboard's freshness signal matches the scheduler's effective cadence instead of depending on whether the user ever opened the heartbeat dropdown. Exports a new `DEFAULT_AGENT_HEARTBEAT_INTERVAL_MS` constant.
## 0.0.4
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@runfusion/fusion",
"version": "0.0.4",
"version": "0.0.5",
"license": "MIT",
"description": "Fusion CLI: HTTP API server, daemon, dashboard launcher, and task tooling for the Fusion AI coding agent.",
"homepage": "https://github.com/Runfusion/Fusion#readme",