Repository navigation
chore: bump eve 0.91.0 + ai 7.0.159; admit eve 1.0 prereleases in eve peers - #86
Merged
Merged
Conversation
… >=0.90.0 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CMK4erbhSW8BMyfyfWiiAG
… peers Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CMK4euGEyks9Y94kQ96Zq9
CahidArda
changed the title
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
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.
Summary
eveto^0.91.0andaito7.0.159(packages, examples, lockfile). The eve-extension dist is rebuilt on 0.91.0; itsevepeer is>=0.91.0 || >=1.0.0-0.npm install eve@latest(now1.0.0-rc.1) fails ERESOLVE against published@upstash/agentkit-eve@0.18.0(peer eve@">=0.87.0") because semver never matches a prerelease against>=0.x. Both eve peers now add|| >=1.0.0-0.eve@1.0.0-rc.1is deliberately NOT adopted as the build base: a dist built on it refuses every 0.x eve. A 0.91.0-built dist verified: eve 0.90.0 refuses it, 0.91.0 and 1.0.0-rc.1eve buildclean.@tanstack/ai1.0.1,-persistence1.0.1,-memory1.0.0) NOT adopted — real break:chat()now requiresthreadIdandArtifactRecordrequiresblobKey;packages/tanstack-aitest files failtscand middleware tests throwchat() needs a threadId. Source and build are fine, published@upstash/agentkit-tanstack-ai@0.2.0installs and imports against 1.0.x. Needs a human to update tests/artifact handling, then raise pins.Verification
lint, typecheck, sync-version --check, build, example builds: pass.
eve evaleve-demo: pass. Live-Redis tests (sdk, ai-sdk, eve, tanstack) and the eve-extension-demo eval'ssearch_countgate failed here only because the throwaway Redis caps at 1 search index (ERR Exceeded max index count of 1) — inconclusive, re-run with a full DB. Blob suites skipped (noUPSTASH_BLOB_TOKEN). Not verified: tanstack e2e (not adopted).🤖 Generated with Claude Code
https://claude.ai/code/session_01CMK4euGEyks9Y94kQ96Zq9