fix!: rebuild eve extension against eve 0.45 and raise its peer floor - #27
Merged
Conversation
`eve extension build` stamps the compatibility manifest with the building eve's current contribution-format versions, and a consumer rejects any version missing from its own supported list. Rebuilding on eve 0.45.0 re-stamps dist/extension/_manifest.json from tool 17 / dynamicTool 18 to tool 18 / dynamicTool 19, and 0.45.0 is the first eve supporting either — every 0.42 through 0.44.4 tops out at tool 17 / dynamicTool 18. So the extension's ">=0.43.0" peer floor no longer describes the built dist: on eve 0.44.3 discovery hard-fails with "requires tool contract v18, but this eve supports tool contract versions: ... v17". - bump eve to ^0.45.0 across packages/eve, packages/eve-extension and both eve demos; the rebuilt manifest stamps formatVersion 2 with tool 18 / dynamicTool 19 / hook 14 / instructions 2 (loads on eve >= 0.45.0 only — 0.45 raised both contracts it stamps, so unlike the 0.44 rebuild there is no back-compat window) - raise the extension's eve peer from ">=0.43.0" to ">=0.45.0" so an incompatible eve fails at install time with an actionable ERESOLVE instead of at eve build - leave packages/eve's eve peer at ">=0.32.0": its source still typechecks cleanly against eve 0.32.0, so no floor change is warranted No source changes were needed. eve 0.45 removed eve/tools/defaults and the defineBashTool/defineReadFileTool/defineWriteFileTool/defineGlobTool/ defineGrepTool factories, and dropped experimental.subagentPersistentSessions (subagent contracts 1 and 2 are now dropped) — AgentKit uses none of them; it imports only defineTool/defineDynamic/SessionContext/ToolContext/ ToolDefinition from eve/tools, defineHook from eve/hooks and defineExtension from eve/extension. ai stays exact-pinned at 7.0.58 (eve 0.45's peer is still ^7.0.58). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ng, poll for async indexing)
CahidArda
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps every
evepin in the repo to 0.45.0, rebuilds@upstash/agentkit-eve-extension's manifest against the new tool/dynamicTool contract versions (17→18, 18→19) and raises its stale peer floor (>=0.43.0→>=0.45.0) so a consumer can't install an eve that fails ateve build; also fixes a nested AGENTS.md note that still told future agents to keep the old floor.On top of that, this fixes the CI red that was blocking the PR:
packages/sdk/src/chat-history.test.tsandpackages/eve/src/search-tools.test.tswere flaking against live Upstash Redis Search independently of the eve bump (reproduced identically onmain). Root cause was two-fold — the search index has to already exist before a doc is written or the create-time backfill drops that doc permanently, andwaitIndexing()is a no-op on a not-yet-existing index — so both tests now provision the index before seeding and poll for the expected result instead of asserting on the first read; no assertion's expected behavior changed. Verified 10/10 clean runs on a fresh Redis where the baseline was 4/10.CLAUDE.md documents the real indexing-order mechanism, and
packages/eve-extension's changeset/README already carry the version bump.Built by upstash-tag · mission
38815da1-2d40-487b-9073-a70e9116dbb7·chore/eve-compat-0.45.0→main· $25.23