From d19c53089d84ebf3eb628f80a0bd16bb07c042ed Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 6 Aug 2026 04:05:39 +0000 Subject: [PATCH] Version Packages --- .changeset/agents-listing-system-channel.md | 5 ---- .../flush-dev-workflow-stream-headers.md | 5 ---- .../mount-workspace-deps-in-dev-snapshots.md | 12 -------- .../unified-session-operation-surfaces.md | 15 ---------- packages/eve/CHANGELOG.md | 29 +++++++++++++++++++ packages/eve/package.json | 2 +- 6 files changed, 30 insertions(+), 38 deletions(-) delete mode 100644 .changeset/agents-listing-system-channel.md delete mode 100644 .changeset/flush-dev-workflow-stream-headers.md delete mode 100644 .changeset/mount-workspace-deps-in-dev-snapshots.md delete mode 100644 .changeset/unified-session-operation-surfaces.md diff --git a/.changeset/agents-listing-system-channel.md b/.changeset/agents-listing-system-channel.md deleted file mode 100644 index 245e434f5..000000000 --- a/.changeset/agents-listing-system-channel.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"eve": patch ---- - -Agent-messaging `` listings are now announced as framework-injected user-role notes instead of assistant messages appended to history. This fixes parent resume failures on models that reject assistant-final requests (e.g. `This model does not support assistant message prefill` from Claude via AI Gateway) after a persistent child parks, keeps the announcement append-only so provider prompt caches stay warm, and the agent-messaging system prompt now declares the `[Agents]` note as framework-injected. diff --git a/.changeset/flush-dev-workflow-stream-headers.md b/.changeset/flush-dev-workflow-stream-headers.md deleted file mode 100644 index 2cdb1aa39..000000000 --- a/.changeset/flush-dev-workflow-stream-headers.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"eve": patch ---- - -Flush local development streaming response headers immediately so pending Workflow streams can be cancelled without accumulating listeners. diff --git a/.changeset/mount-workspace-deps-in-dev-snapshots.md b/.changeset/mount-workspace-deps-in-dev-snapshots.md deleted file mode 100644 index 4ffdb3f2d..000000000 --- a/.changeset/mount-workspace-deps-in-dev-snapshots.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -"eve": patch ---- - -Dev runtime snapshots now mount workspace dependency packages in place -instead of copying them. Only roots that host runtime-hydrated authored -source — the app root, extension mount roots, and tsconfig path-alias -targets — are still copied, matching how installed dependencies already -resolved. In monorepos this removes the largest per-generation copy: a -workspace-linked framework package (hundreds of files and tens of -megabytes per rebuild) no longer lands under -`.eve/dev-runtime/snapshots/`. diff --git a/.changeset/unified-session-operation-surfaces.md b/.changeset/unified-session-operation-surfaces.md deleted file mode 100644 index 23cacdb26..000000000 --- a/.changeset/unified-session-operation-surfaces.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -"eve": minor ---- - -Replace continuation-token session APIs with fixed, ID-addressed handles and consistent channel-local operations. This is a breaking migration across the following public surfaces: - -- TypeScript clients now use `client.sessions.create(input)` to start a session and `client.sessions.attach(sessionId)` to obtain a fixed handle; `client.session(...)` and continuation-token client state are removed. -- Client, eval, frontend, fixed-session, and Slack message delivery now use positional `send(message, options)`. HITL replies use the separate `respond(inputResponses, options)` method, and `message` and `inputResponses` are mutually exclusive. -- Custom channels use `from(address)` for channel-local operations, top-level `resolveSession(address)` to resolve the current owner, `attachSession(sessionId)` for an immutable session handle, and `to(channel, target)` for cross-channel delivery. -- Slack message and interaction hooks expose `ctx.send`, `ctx.respond`, `ctx.cancel`, `ctx.compact`, `ctx.clear`, `ctx.reset`, and `ctx.resolveSession`. For generic events, the target is passed in each operation's options; `ctx.receive` and `resolveActiveSession` are removed. -- Schedule handlers replace `receive(channel, { message, target, auth })` with `to(channel, target).send(message, { auth })`. -- Channel event session identity moves to `ctx.session.id`, while `session.failed` includes `sessionId` in its event data. -- The eve HTTP API keeps `POST /eve/v1/session` for creation and `POST /eve/v1/session/:sessionId` for follow-ups. Clear, compact, and reset move from continuation-token body routes to `POST /eve/v1/session/:sessionId/{clear,compact,reset}`; cancel and streaming remain ID-addressed. -- Session message and control bodies no longer accept or return continuation tokens. Accepted asynchronous work returns HTTP `202`; no-active operation results omit `sessionId`, and inactive follow-ups return HTTP `409` with `code: "session_not_active"`, available as `ClientError.code`. -- Canonical eve `onMessage` hooks can no longer drop an otherwise authorized delivery by returning `null`. diff --git a/packages/eve/CHANGELOG.md b/packages/eve/CHANGELOG.md index 5ddc80f39..b44857ec9 100644 --- a/packages/eve/CHANGELOG.md +++ b/packages/eve/CHANGELOG.md @@ -1,5 +1,34 @@ # eve +## 0.31.0 + +### Minor Changes + +- 40b09e6: Replace continuation-token session APIs with fixed, ID-addressed handles and consistent channel-local operations. This is a breaking migration across the following public surfaces: + + - TypeScript clients now use `client.sessions.create(input)` to start a session and `client.sessions.attach(sessionId)` to obtain a fixed handle; `client.session(...)` and continuation-token client state are removed. + - Client, eval, frontend, fixed-session, and Slack message delivery now use positional `send(message, options)`. HITL replies use the separate `respond(inputResponses, options)` method, and `message` and `inputResponses` are mutually exclusive. + - Custom channels use `from(address)` for channel-local operations, top-level `resolveSession(address)` to resolve the current owner, `attachSession(sessionId)` for an immutable session handle, and `to(channel, target)` for cross-channel delivery. + - Slack message and interaction hooks expose `ctx.send`, `ctx.respond`, `ctx.cancel`, `ctx.compact`, `ctx.clear`, `ctx.reset`, and `ctx.resolveSession`. For generic events, the target is passed in each operation's options; `ctx.receive` and `resolveActiveSession` are removed. + - Schedule handlers replace `receive(channel, { message, target, auth })` with `to(channel, target).send(message, { auth })`. + - Channel event session identity moves to `ctx.session.id`, while `session.failed` includes `sessionId` in its event data. + - The eve HTTP API keeps `POST /eve/v1/session` for creation and `POST /eve/v1/session/:sessionId` for follow-ups. Clear, compact, and reset move from continuation-token body routes to `POST /eve/v1/session/:sessionId/{clear,compact,reset}`; cancel and streaming remain ID-addressed. + - Session message and control bodies no longer accept or return continuation tokens. Accepted asynchronous work returns HTTP `202`; no-active operation results omit `sessionId`, and inactive follow-ups return HTTP `409` with `code: "session_not_active"`, available as `ClientError.code`. + - Canonical eve `onMessage` hooks can no longer drop an otherwise authorized delivery by returning `null`. + +### Patch Changes + +- 2054b9f: Agent-messaging `` listings are now announced as framework-injected user-role notes instead of assistant messages appended to history. This fixes parent resume failures on models that reject assistant-final requests (e.g. `This model does not support assistant message prefill` from Claude via AI Gateway) after a persistent child parks, keeps the announcement append-only so provider prompt caches stay warm, and the agent-messaging system prompt now declares the `[Agents]` note as framework-injected. +- 84c3dfc: Flush local development streaming response headers immediately so pending Workflow streams can be cancelled without accumulating listeners. +- b7a2a14: Dev runtime snapshots now mount workspace dependency packages in place + instead of copying them. Only roots that host runtime-hydrated authored + source — the app root, extension mount roots, and tsconfig path-alias + targets — are still copied, matching how installed dependencies already + resolved. In monorepos this removes the largest per-generation copy: a + workspace-linked framework package (hundreds of files and tens of + megabytes per rebuild) no longer lands under + `.eve/dev-runtime/snapshots/`. + ## 0.30.8 ### Patch Changes diff --git a/packages/eve/package.json b/packages/eve/package.json index 52ae125f9..cd57d6a7a 100644 --- a/packages/eve/package.json +++ b/packages/eve/package.json @@ -1,6 +1,6 @@ { "name": "eve", - "version": "0.30.8", + "version": "0.31.0", "private": false, "description": "Filesystem-first framework for durable backend AI agents that run anywhere.", "keywords": [