Skip to content

armgit / eve

Public Imported from GitHub
0

The Open Framework for Building Agents

Version Packages (#505)

github-actions[bot]c61ea67b02f1
diff --git a/.changeset/eval-nested-dir-error.md b/.changeset/eval-nested-dir-error.md
deleted file mode 100644
index a1cce5dde..000000000
--- a/.changeset/eval-nested-dir-error.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"eve": patch
----
-
-`eve eval` now prints a clear, actionable message when it finds no evals but detects `*.eval.ts` files placed inside `agent/`. Instead of the generic "No evals found", it names the offending directories and reminds you that eval files belong in the top-level `evals/` directory (a sibling of `agent/`).
diff --git a/.changeset/expose-tool-call-id.md b/.changeset/expose-tool-call-id.md
deleted file mode 100644
index ae30b0240..000000000
--- a/.changeset/expose-tool-call-id.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"eve": patch
----
-
-`ToolContext` and `ApprovalContext` now expose `callId`, the tool call id carried by the call's stream events, so approval-gated tools can key records to one identity across proposal, rejection, and execution.
diff --git a/.changeset/honor-missing-attachment-on-resume.md b/.changeset/honor-missing-attachment-on-resume.md
deleted file mode 100644
index b3ec50d4b..000000000
--- a/.changeset/honor-missing-attachment-on-resume.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"eve": patch
----
-
-Resuming a durable session whose history references a file attachment no longer fails the turn when the staged bytes are gone (for example after a redeploy pointed the session at a fresh sandbox). The missing attachment degrades to a `FileNotFound` text notice the model can interpret, so the run continues instead of ending in `session.failed`.
diff --git a/.changeset/sandbox-server-shutdown-cleanup.md b/.changeset/sandbox-server-shutdown-cleanup.md
deleted file mode 100644
index d3b7afe26..000000000
--- a/.changeset/sandbox-server-shutdown-cleanup.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"eve": minor
----
-
-Sandboxes are now stopped when the eve server shuts down. Self-hosted production servers stop every open sandbox (microsandbox VMs, Docker containers, Vercel sandboxes, just-bash interpreters) on `SIGTERM`/`SIGINT`, matching the cleanup `eve dev` already performs, and sessions reattach from persisted state on the next start. Breaking change for custom sandbox backends: `SandboxBackendHandle` gains a required `shutdown()` and the unused `dispose()` is removed.
diff --git a/.changeset/turn-cancellation-harness-abort.md b/.changeset/turn-cancellation-harness-abort.md
deleted file mode 100644
index fbfce76d4..000000000
--- a/.changeset/turn-cancellation-harness-abort.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"eve": patch
----
-
-The turn harness now propagates a cooperative `AbortSignal` end to end: model calls, retries, recovery, compaction, and tool executions all honor it, and an aborted turn settles with a canonical `TurnCancelledError` that is never retried or misclassified as a failure. Authored tools receive the signal as `ctx.abortSignal` (and via the AI SDK execute options), and framework tools forward it into sandbox commands, file I/O, `web_fetch`, and MCP/OpenAPI connection calls. This is the lowest layer of turn cancellation — no trigger exists yet, so runtime behavior is unchanged until the cancellation API ships.
diff --git a/packages/eve/CHANGELOG.md b/packages/eve/CHANGELOG.md
index cf8e79374..268762762 100644
--- a/packages/eve/CHANGELOG.md
+++ b/packages/eve/CHANGELOG.md
@@ -1,5 +1,18 @@
# eve
+## 0.20.0
+
+### Minor Changes
+
+- 6f9364a: Sandboxes are now stopped when the eve server shuts down. Self-hosted production servers stop every open sandbox (microsandbox VMs, Docker containers, Vercel sandboxes, just-bash interpreters) on `SIGTERM`/`SIGINT`, matching the cleanup `eve dev` already performs, and sessions reattach from persisted state on the next start. Breaking change for custom sandbox backends: `SandboxBackendHandle` gains a required `shutdown()` and the unused `dispose()` is removed.
+
+### Patch Changes
+
+- 7699e98: `eve eval` now prints a clear, actionable message when it finds no evals but detects `*.eval.ts` files placed inside `agent/`. Instead of the generic "No evals found", it names the offending directories and reminds you that eval files belong in the top-level `evals/` directory (a sibling of `agent/`).
+- f3a05c5: `ToolContext` and `ApprovalContext` now expose `callId`, the tool call id carried by the call's stream events, so approval-gated tools can key records to one identity across proposal, rejection, and execution.
+- f9621b6: Resuming a durable session whose history references a file attachment no longer fails the turn when the staged bytes are gone (for example after a redeploy pointed the session at a fresh sandbox). The missing attachment degrades to a `FileNotFound` text notice the model can interpret, so the run continues instead of ending in `session.failed`.
+- c233a6a: The turn harness now propagates a cooperative `AbortSignal` end to end: model calls, retries, recovery, compaction, and tool executions all honor it, and an aborted turn settles with a canonical `TurnCancelledError` that is never retried or misclassified as a failure. Authored tools receive the signal as `ctx.abortSignal` (and via the AI SDK execute options), and framework tools forward it into sandbox commands, file I/O, `web_fetch`, and MCP/OpenAPI connection calls. This is the lowest layer of turn cancellation — no trigger exists yet, so runtime behavior is unchanged until the cancellation API ships.
+
## 0.19.0
### Minor Changes
diff --git a/packages/eve/package.json b/packages/eve/package.json
index d0fba6059..ee43003d2 100644
--- a/packages/eve/package.json
+++ b/packages/eve/package.json
@@ -1,6 +1,6 @@
{
"name": "eve",
- "version": "0.19.0",
+ "version": "0.20.0",
"private": false,
"description": "Filesystem-first framework for durable backend AI agents that run anywhere.",
"keywords": [