Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@upstash/agentkit-eve@0.13.0

Minor Changes

• 8b8163e: feat!: port the Upstash Box sandbox to eve's sandbox provider API (UpstashSandbox), and require
  eve >=0.65.0 and @upstash/box >=0.7.1

  eve 0.64.0 removed sandbox backends: the SandboxBackend* types upstash() implemented and the
  object form defineSandbox({ backend, bootstrap, onSession }) it plugged into. On eve ≥0.64,
  @upstash/agentkit-eve/sandbox could still be imported, but nothing could use it, and its types
  no longer compiled. It is replaced by an eve sandbox provider, used like eve's VercelSandbox:

  // agent/sandbox.ts
  import { defineSandbox } from "eve/sandbox";
  import { UpstashSandbox } from "@upstash/agentkit-eve/sandbox";
  
  export const environment = UpstashSandbox.environment({
    runtime: "node",
    async prepare(sandbox) {
      await sandbox.setNetworkPolicy("allow-all");
      await sandbox.run({ command: "sudo apt-get install -y jq" });
    },
  });
  
  export default defineSandbox(() => environment.open());

  Migrating from upstash(): bootstrap becomes the environment's prepare, onSession's
  use({ networkPolicy }) becomes environment.open({ networkPolicy }), and revalidationKey goes away.
  The redis, templatePrefix and enableTelemetry options are removed: the prepared Box snapshot id is
  now stored in eve's build output, so the Redis template registry is no longer needed. name is no
  longer accepted, because every session gets its own uniquely named box.

  Behaviour changes, all following eve's provider contract:

  • Prepare runs at eve build and bakes eve's workspace seeds, skills ($HOME/.agents/skills,
    new) and your prepare hook into one Box snapshot. With nothing to bake, no box is created.
  • Resume reattaches to the session's box and fails if it is gone, instead of silently creating
    an empty one; sandbox.delete() starts a fresh box. A deleted prepared snapshot also fails loudly
    with rebuild/redeploy guidance, instead of falling back to an empty box.
  • Commands run over Box's streaming exec sessions: stdout and stderr are separate (previously the
    combined output was reported as stderr on failure), env reaches every command in a && chain, and
    a cancelled turn kills the running command (previously it kept running). spawn streams output
    live instead of replaying it after exit.
  • Network egress stays deny-all by default; Box keeps the policy on the box across pause/resume.

  The package's eve peer moves >=0.45.2 → >=0.65.0 for all entry points; memory, tools, auth
  and search are otherwise unchanged. @upstash/box (optional peer) moves >=0.5.0 → >=0.7.1.

  Verified against real Upstash Box: the full prepare → start → stop → resume → delete cycle, streaming
  and kill, abort, and network policies. Also verified end to end: eve build plus a two-turn eval in
  which eve's built-in bash tool read the seeded workspace, a skill and the prepare output, and read a
  file written in turn 1 back in turn 2.

@upstash/agentkit-eve-extension@0.13.0

Minor Changes

• 8b8163e: fix!: rebuild the extension against eve 0.65.0 and raise the eve peer floor to >=0.65.0 —
  0.12.0 cannot build on any eve released after it

  0.12.0 ships a dist/extension/_manifest.json built with eve 0.63.0, stamping tool contract
  53, dynamicTool 51 and hook 24. eve 0.64.0 dropped all three at once, while
  0.12.0's peer range ">=0.63.0" still admits it. So
  npm install eve@latest @upstash/agentkit-eve-extension@latest resolves cleanly, and then the first
  eve build fails with the one-line error eve reports for a mount it cannot use:

  Selected module binding "extensions/agentkit.ts" has no compile or runtime usage.
  

  Nothing catches it earlier: the install is silent, and the error never mentions contracts, versions
  or the extension package. eve dev, eve eval and eve start fail the same way. Verified on a fresh
  consumer with eve 0.64.1 and 0.65.0 (the current latest).

  The rebuilt dist stamps tool 55 / dynamicTool 52 / hook 25 (builtWithEve 0.65.0). 0.65.0 is the
  first eve accepting tool 55, so the peer moves ">=0.63.0" → ">=0.65.0" and an eve that cannot
  run this dist is rejected at install (ERESOLVE) instead of failing at build time.

  No behaviour changed and no API changed: the same extension source recompiled against a newer
  eve. Every contribution is unchanged (recall_memory / save_memory, the dynamic search /
  search_aggregate / search_count and search_chat_history / read_chat_history tools, the
  chat_history hook and the memory instructions fragment), and the zod: "^4.4.3" range 0.12.0
  shipped for the dual-zod dedupe fix is kept.

  If you are pinned to eve 0.63.0, stay on 0.12.0.

eve-demo@0.0.12

Patch Changes

• Updated dependencies [8b8163e]
  • @upstash/agentkit-eve@0.13.0

eve-extension-demo@0.0.12

Patch Changes

• Updated dependencies [8b8163e]
  • @upstash/agentkit-eve-extension@0.13.0