Skip to content

fix(deps): admit Eval 0.199 in Knowledge's peer range - #226

Merged
drewstone merged 1 commit into
mainfrom
fix/eval-0199-peer
Sep 27, 2026
Merged

drewstone merged 1 commit into
mainfrom
fix/eval-0199-peer

Conversation

@drewstone

Copy link
Copy Markdown
Contributor

Widen the Eval peer range to >=0.182.0 <0.200.0, add 0.199.0 to evalCompatibility's verified list, and move the development pin to 0.199.0. Version 17.1.10.

Why: Knowledge 17.1.9 caps Eval below 0.199.0, so agent-runtime cannot install Eval 0.199.0 beside Knowledge under strict peers. Runtime needs 0.199.0 for incumbent({ patience, minImprovement }) (agent-eval #878), which the pursuit version chain on the search kernel uses (search-tree package R4).

Eval 0.199.0 adds an option and changes the leader rule when a leader has no scored unit; it removes nothing, and Knowledge imports no search policy.

Proof (drew-gtr-pro, Node 22.23.2, at 73415a8):

  • pnpm install resolves agent-eval 0.199.0 (lockfile moves 0.198.0 to 0.199.0 only).
  • pnpm typecheck passes; pnpm run lint passes; pnpm run build passes.
  • node scripts/verify-package.mjs -> Verified @tangle-network/agent-knowledge@17.1.10 with one installed copy each of agent-eval 0.199.0, agent-core 0.9.7, agent-interface 2.0.0, and zod 4.5.4: clean install, portable declarations, 5 imports, skill, CLI version, and re-pack.

Widen the peer range to >=0.182.0 <0.200.0 and add 0.199.0 to evalCompatibility's verified list; the development pin moves to 0.199.0. Knowledge 17.1.9 caps Eval below 0.199.0, so agent-runtime cannot install Eval 0.199.0 (incumbent minImprovement, which the pursuit version chain on the search kernel needs, search-tree package R4) beside Knowledge under strict peers.
@drewstone
drewstone merged commit 20e8f44 into main Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant