fix!: rebuild eve extension against eve 0.44 so it loads on current eve - #23
Merged
Conversation
The published extension was built with eve 0.32.0, stamping hook contract v9 in dist/extension/_manifest.json — a contract eve 0.33.0 dropped, so the extension failed eve build on every eve released after 0.32.0. - bump eve to ^0.44.3 across packages/eve, packages/eve-extension and both eve demos; the rebuilt manifest stamps formatVersion 2 with tool 17 / dynamicTool 18 / hook 14 / instructions 2 (loads on eve >= 0.43.0) - tighten the extension's eve peer from "*" to ">=0.43.0" so an incompatible eve fails at install time with an actionable message instead of at eve build - correct packages/eve's eve peer from >=0.24.0 to >=0.32.0 (the Box sandbox backend implements the stop() handle contract eve requires since 0.32) No source changes were needed; ai stays exact-pinned at 7.0.58 (eve 0.44's peer is still ^7.0.58). Fixes #22
CahidArda
added a commit
that referenced
this pull request
Aug 24, 2026
The extension demo now doubles as the extension's end-to-end smoke test, written as an eve eval (evals/agentkit-smoke.eval.ts). AGENTKIT_MOCK_MODEL=1 switches agent/agent.ts to a deterministic mockModel from eve/evals whose scripted response calls agentkit__save_memory and then echoes the tool result — no model provider needed, only Redis credentials. A green run proves the built extension loads on the installed eve, its contributions mount, a session runs end to end, the tool writes to Redis, and the chat_history hook captures the turn. The mocked branch sets modelContextWindowTokens because the mock model has no AI Gateway metadata (compaction fails to compile without it), and uses mockModel's plain-callback form (a custom identity hits the same error). Documented in both the demo and package READMEs; also corrected the extension AGENTS.md, which still told authors to keep the eve peer a wildcard (superseded by the >=0.43.0 floor from #23).
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.
The published extension was built with eve 0.32.0, stamping hook contract v9 in dist/extension/_manifest.json — a contract eve 0.33.0 dropped, so the extension failed eve build on every eve released after 0.32.0.
No source changes were needed; ai stays exact-pinned at 7.0.58 (eve 0.44's peer is still ^7.0.58).
Fixes #22