Repository navigation
chore(eve-extension): rebuild against eve 0.70.0, raise peer floor to >=0.70.0 - #55
Closed
upstash-tag[bot] wants to merge 3 commits into
Closed
upstash-tag[bot] wants to merge 3 commits into
upstash-tag[bot] wants to merge 3 commits into
Conversation
… >=0.70.0 eve 0.70.0 adds tool contracts 72-73, dynamicTool 69-70 and hook 36-37 and drops none, so published 0.15.0 keeps working on it. Rebuilding on 0.70.0 re-stamps the manifest to tool 73 / dynamicTool 70 / hook 37, which only eve >= 0.70.0 accepts (a packed rebuilt dist fails `eve build` on 0.69.0), so the extension's eve peer moves >=0.69.0 -> >=0.70.0. - packages/eve-extension + examples/eve-extension-demo: eve ^0.69.0 -> ^0.70.0 - packages/eve-extension peer eve: >=0.69.0 -> >=0.70.0, README/AGENTS.md updated - changeset (minor) for @upstash/agentkit-eve-extension - CLAUDE.md: 0.69.0 -> 0.70.0 bump note and current-state refs; pnpm 11.5.3 must be first on PATH in the agent box - eve's ai peer is still ^7.0.105: ai pin unchanged packages/eve stays on eve ^0.65.0 (sandbox.ts MutableNetworkSandboxSession port is tracked separately). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
eve shipped 0.70.1 and 0.70.2 while this PR was open. Their capability tables are identical to 0.70.0, so the rebuilt manifest still stamps tool 73 / dynamicTool 70 / hook 37 (builtWithEve 0.70.2) and the peer floor stays >=0.70.0. Re-measured with packed consumers: the dist fails `eve build` on 0.69.0 and builds on 0.70.0 and 0.70.2. packages/eve and examples/eve-demo stay on 0.65.0: on 0.70.2, src/sandbox.ts(63,3) still fails with TS2305 (MutableNetworkSandboxSession). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Daily eve-compat check found eve's npm latest moved to 0.70.0, which re-stamps
packages/eve-extension's built manifest (tool 73 / dynamicTool 70 / hook 37, up from 71/68/35 on eve 0.69.0). This rebuilds the extension's dist against 0.70.0 and raises itsevepeer floor from>=0.69.0to>=0.70.0so an incompatible eve is rejected at install instead of failing later ateve build— verified by packing the rebuilt tarball into fresh consumers: eve 0.69.0 is rejected (ERESOLVE) / failseve buildunder--legacy-peer-deps, eve 0.70.0 installs and builds clean with all 8 extension contributions mounted.This isn't a fix for a break: the currently-published
@upstash/agentkit-eve-extension@0.15.0still works on both eve 0.69.0 and 0.70.0 (eve 0.70.0 only added contract numbers, it dropped none), so the changeset notes this explicitly.packages/eveis untouched and stays pinned to eve ^0.65.0 — itssandbox.tsimport ofMutableNetworkSandboxSession(removed by eve in 0.66.0) is a separate, already-tracked source-level port, out of scope for this mechanical bump. Also updates the extension's README/AGENTS.md and CLAUDE.md's eve compatibility notes, plus a correction to CLAUDE.md's existing pnpm-11.5.3-on-PATH note (the documentednpm i -ginstall hit a permissions error in this box; installing under~/.local/pnpm11and prepending it to PATH is what actually works).Built by upstash-tag · mission
5eaa7f34-8067-4c46-a973-83fa43834c7f·chore/eve-extension-eve-0.70.0→main· $11.26