eve-extension 0.6.0 cannot load on eve 0.33.0+ (hook contract v9 dropped)

[Josh-moreton]

@upstash/agentkit-eve-extension@0.6.0 fails at eve build on any eve release newer than 0.32.0:

Extension "@upstash/agentkit-eve-extension" requires hook contract v9,
but this eve supports hook contract versions: v10, v11, v12, v13.
Upgrade eve or install an extension release that requires a supported hook contract.
source: node_modules/@upstash/agentkit-eve-extension/dist/extension/_manifest.json

Cause

The published dist/extension/_manifest.json in 0.6.0 stamps:

{ "builtWithEve": "0.32.0", "requires": { "hook": 9, ... } }

eve 0.33.0 dropped hook contracts 1–9 — released 2026-08-11 19:55, about nine hours after 0.32.0 (10:13). eve's own compatibility table gives the reason: "Model identity moved from session.started runtime metadata to step.started call attribution."

eve	supported hook contracts
0.32.0	[1..9]
0.33.0	[10]
0.36.0	[10, 11, 12]
0.39.x	[10, 11, 12, 13]

#17 (feat!: upgrade to eve 0.32) is the most recent eve bump, so 0.6.0 — published 2026-08-18, five days after eve had already moved to 0.33 — still targets the one release that supports v9.

Two requests

1. Rebuild against a current eve so the extension requires hook v10+. Right now 0.32.0 is the only eve release AgentKit can run on, which pins consumers seven minors behind.

2. Tighten the peer range. package.json declares peerDependencies: { "eve": "*" }, so npm and pnpm install cleanly and the incompatibility only surfaces at build time. Something like "eve": "0.32.x" would fail at install with an actionable message instead.

Repro

npm install eve@0.39.1 @upstash/agentkit-eve-extension@0.6.0
# agent/extensions/agentkit.ts:
#   import agentkit from "@upstash/agentkit-eve-extension";
#   export default agentkit();
npx eve build

Builds fine on eve@0.32.0; fails on 0.33.0 and every release after.

Also worth updating https://upstash.com/docs/redis/sdks/agentkit/eve — it currently states "eve 0.25.2 or later", but the working range is effectively 0.32.0 only.

[CahidArda]

Thanks a lot for letting us know @Josh-moreton, released a new version to fix the issue. Let us know if you encounter any other issues!