[kjgbot]

Why

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

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

Change

• Pin @relayflows/cli 1.1.9 (fix(core): accept @agent-relay/* 16 alongside 12 relayflows#66). Its core accepts ^12.2.2 || ^16.0.0, so it dedupes onto this repo's 16 packages and broker. No @agent-relay 12.x entries remain in the lockfile.
• The lockfile also syncs the workspace versions that the v16.0.0 release commit left at 15.1.1. The release workflow discards lockfile changes, so main's lock still said 15.1.1.
• CHANGELOG: one line under [Unreleased - Major] / Fixed.

Note: this lands on main after #2069, so it ships in the next release from main (17.0.0).

Tests (local)

• npm ci is clean.
• npm run typecheck passes.
• peer-compat, cloud-worker and cloud-worker-cli-credentials tests: 31/31 pass.
• A worker image built as agent-relay 16.0.0 with an override to @relayflows/cli 1.1.9 resolves a single @agent-relay/sdk 16.0.0 (deduped) and a single 16.0.0 broker.

🤖 Generated with Claude Code

---

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

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The CLI dependency changes from version 1.1.8 to 1.1.9. The changelog records a fix for Cloud worker flows against self-hosted Relay instances.

Changes: CLI Version Update

Layer / File(s)	Summary
CLI dependency and release note packages/cli/package.json, CHANGELOG.md	The package manifest updates @relayflows/cli from 1.1.8 to 1.1.9. The changelog records a fix for Cloud worker flows against self-hosted Relay instances. It states that flows no longer fail with failed to initialize relaycast session or run on an old bundled broker.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other · Severity of issue fixed: Medium

Possibly related PRs

• AgentWorkforce/relay#843: Adds the Cloud worker path that runs workflows through @relayflows/cli, the dependency updated here.
• AgentWorkforce/relay#2073: Adds credential mounting and write-back for the Cloud worker, which runs flows through the updated CLI dependency.
• AgentWorkforce/relay#2077: Pins @relayflows/cli to 1.1.8 for Cloud worker login precedence; this change updates that dependency to 1.1.9.

Merge Risk: Minimal · up to b057e

The dependency update supports using the Relay 16 broker for Cloud worker flows. No merge-blocking issue was identified; merge after normal checks pass.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description covers the Why, Change, and Tests sections, and explains the root cause (the nested 12.4.1 broker) with the reported error text. It also lists the local test results. The template's Re…	Fill in the RelayFlow Proof section. Set the change type to bugfix, since this is a user-visible fix, and replace the replace-me case placeholder with the case ID for the new case under tests/relayflows/cases/<case-id>/. Add that test…

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title names the main change: pinning @relayflows/cli to 1.1.9 so flows run on the Relay 16 broker. The raw summary confirms the package.json bump from 1.1.8 to 1.1.9 and a CHANGELOG Fixed entry. T…
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: pinning @relayflows/cli to 1.1.9 so flows run on the Relay 16 broker. The raw summary confirms the package.json bump from 1.1.8 to 1.1.9 and a CHANGELOG Fixed entry. The title is specific, concise, and follows a conventional commit style. It omits the lockfile sync and the changelog entry, which is acceptable because they are secondary.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Full details: Description check

Explanation

The description covers the Why, Change, and Tests sections, and explains the root cause (the nested 12.4.1 broker) with the reported error text. It also lists the local test results. The template's RelayFlow Proof section is not filled in: the change type and RelayFlow case placeholders still read replace-me. The Test Plan checkboxes are not ticked, and the Screenshots section is absent. The Summary heading is replaced by Why/Change/Tests sections.

Resolution

Fill in the RelayFlow Proof section. Set the change type to bugfix, since this is a user-visible fix, and replace the replace-me case placeholder with the case ID for the new case under tests/relayflows/cases/<case-id>/. Add that test case. Tick the Test Plan checkboxes that apply, or state why manual testing was not done. Note the Screenshots section as not applicable if no screenshots exist.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the version in the snow,
The worker starts where self-hosted flows must go.
No stale broker waits along the way,
Relaycast welcomes flows to play.
One small bump, then off we hop,
Through fields of code from hop to hop.}

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: a0d38950-23bd-4f57-91a3-e1c64c485d18

Commits

Reviewing files that changed from the base of the PR and between ac37bc4 and b057e7d.

Files selected for processing: 1

• CHANGELOG.md

Files skipped from review as they are similar to previous changes: 1

• CHANGELOG.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge with no new actionable issues.

Summary

Pins @relayflows/cli to 1.1.9 and updates the changelog to describe the flow startup fix.

• Cloud worker flows use the Relay 16 broker.
• The lockfile tracks the workspace packages at version 16.0.0.

_{Reviews (2) · Last reviewed commit: "docs(changelog): Fixed after Removed; st..." · Reviewed by Greptile}

[cubic-dev-ai]

All reported issues were addressed across 3 files

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>