fix(core): accept @agent-relay/* 16 alongside 12

Merged
KJ
9d ago
+61-62

Why

agent-relay 16.0.0 pins @relayflows/cli 1.1.8. Its @relayflows/core depends on @agent-relay/{sdk,cloud,config,harness-driver,harnesses} ^12.2.2.

  • In a stock install (for example npm i -g agent-relay@16.0.0), npm nests the 12.4.1 packages under core. agent-relay cloud worker then runs flows on the 12.4.1 broker.
  • On the self-hosted proof (gcp-proof), that broker fails at startup with failed to initialize relaycast session / HTTP error: error decoding response body. The same worker with the 16.0.0 broker in that slot completes the run.

Change

  • packages/core: @agent-relay/* ranges ^12.2.2 -> ^12.2.2 || ^16.0.0. Core then dedupes onto agent-relay's own 16.0.0 packages and broker, and 12 stays supported.
  • package-lock.json: those packages resolve to 16.0.0, so this repo's CI now runs against Relay 16.

Tests (local)

  • npm run typecheck passes.
  • npm test: 65 files, 1130/1130 pass, with the @agent-relay 16.0.0 packages installed.

After merge

Release through publish.yml (package=all, patch -> 1.1.9). Then bump agent-relay's @relayflows/cli pin and publish agent-relay 16.0.1.

🤖 Generated with Claude Code

Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.