chore: bump to eve 0.52.3, raise eve-extension peer floor to >=0.52.3 - #39
Open
upstash-tag[bot] wants to merge 1 commit into
Open
chore: bump to eve 0.52.3, raise eve-extension peer floor to >=0.52.3#39upstash-tag[bot] wants to merge 1 commit into
upstash-tag[bot] wants to merge 1 commit into
Conversation
Rebuilds packages/eve-extension against eve 0.52.3, re-stamping its compatibility manifest (tool 30->32, dynamicTool 29->31, hook 20->22) and raising its eve peer floor to match. packages/eve's devDependency moves too but its published dist is byte-identical (verified by diffing dist/ built against 0.52.2 vs 0.52.3), so it gets no changeset. Docs (CLAUDE.md, eve-extension README/AGENTS.md) updated to match.
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.
Note
upstash-tag is still working on this. The description and evidence below
are rewritten when the mission finishes — follow it live.
Moves every
evepin in the repo (packages/eve, packages/eve-extension, examples/eve-demo, examples/eve-extension-demo) from ^0.52.2 to ^0.52.3, the current npmlatest. Rebuildingpackages/eve-extensionagainst 0.52.3 re-stamps its compatibility manifest (tool 30→32, dynamicTool 29→31, hook 20→22), so itsevepeer floor moves>=0.52.2→>=0.52.3to match what the rebuilt dist actually requires — otherwise the next publish would silently claim support for 0.52.2 it no longer has.packages/eveonly moves its devDependency: its builtdistis byte-identical before and after the bump (diffed directly), so it ships no changeset — only@upstash/agentkit-eve-extensiongets one, worded against the last published version (0.10.0) per the repo's one-changeset-per-changed-package convention. CLAUDE.md, the extension's README and AGENTS.md are updated to match the new version/contract numbers.Verified: a fresh npm consumer installing
eve@latest+ both packages@latestbuilds clean today (this bump doesn't fix a break — eve 0.52.3 kept accepting the old contract 30, it just added newer ones); the repo builds, typechecks and lints clean with these pins; and the rebuilt extension mounts correctly under 0.52.3 in a packed-tarball check. Redis-backed tests and the mocked eval could not be exercised in this sandbox (*.upstash.ioegress is blocked here) but nothing in that path depends on the eve version.Built by upstash-tag · mission
bb023ce4-de82-43db-8931-828ecf139ff4·chore/eve-0.52.3→main