chore(cli): pin @relayflows/sdk 2.0.66 so 18.0.0 installs beside it

Merged
KH
4d ago
+15-15

Why

The 18.0.0 publish (run 42576272570) failed in Build & Version. relayflows-peer-compat.test.ts hit ERESOLVE because @relayflows/sdk@2.0.65's optional @agent-relay/sdk peer stops at <18. Nothing was published.

flows #709 widened that peer to <19, and it's published as @relayflows/sdk 2.0.66. #709 is the only flows change since 2.0.65.

Change

  • Pins @relayflows/sdk 2.0.66 in package.json, packages/cli/package.json and the product-surfaces.ts range.
  • Updates the exact version that the GitLab released-pins case checks.
  • Lockfile: only the two @relayflows entries and the two pin lines change.
    • A full npm install --package-lock-only also moved @agent-relay/sdk off its workspace link to a registry copy under packages/cli, and marked packages/sdk extraneous.
    • That doesn't happen on untouched main, so I kept those entries as they are on main, the same as the Relay 17 pin (5a9f0b78f).
  • No changelog entry: this only unblocks the release.
  • The root overrides entry stays unchanged; the publish workflow rewrites it during the version bump.

Validation

  • Lockfile: integrity hashes match the registry for @relayflows/sdk and @relayflows/surface 2.0.66. npm ci accepts the lockfile, and npm ls shows @agent-relay/sdk linked to ./packages/sdk.
  • Peer-compat test: relayflows-peer-compat.test.ts passes at 17.2.1, and again with the CLI version set to 18.0.0, which is the case that failed the release.
  • Typecheck: npm run typecheck passes.
  • Full suite: I couldn't complete it locally because the disk filled up (ENOSPC), so CI is the full-suite check.

After merge

Rerun the 18.0.0 publish (package=all, version=major).

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