chore(deps): bump relaycast SDKs to latest#1203
Conversation
Upgrade every relaycast SDK dependency to its latest published version:
- npm @relaycast/sdk ^4.1.6 -> ^5.0.5 (v4->v5 major) in packages/sdk + packages/cli
- Rust relaycast crate =5.0.1 -> =5.0.2 in crates/broker
- PyPI relaycast-sdk >=0.2.0 -> >=0.3.0 (communicate + dev extras)
- Swift relaycast git dep 4.2.0 -> 5.0.5
v5 migration: agents.release now returns an action invocation (matching
agents.spawn) instead of the synchronous { name, removed, deleted, reason }
result. The remove_agent MCP tool now surfaces that invocation via jsonResult.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughRelaycast SDK version pins were updated across the CLI, SDK, broker, Python, and Swift packages, and ChangesRelaycast SDK upgrade and MCP invocation response
Sequence Diagram(s)sequenceDiagram
participant MCPClient
participant remove_agent
participant RelaycastSDK
MCPClient->>remove_agent: name, reason, deleteAgent
remove_agent->>RelaycastSDK: agents.release({ name, reason, deleteAgent })
RelaycastSDK-->>remove_agent: invocation
remove_agent-->>MCPClient: { invocation }
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request upgrades the relaycast SDKs across multiple languages and packages to their latest versions, including a major version bump (v4 to v5) for @relaycast/sdk. This major upgrade changes agents.release to return an action invocation, and the remove_agent MCP tool in the CLI has been updated accordingly. The review feedback correctly points out that, per the repository style guide, this breaking change should be documented under a ### Breaking Changes section in the changelog rather than ### Changed.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - relaycast SDKs upgraded to latest: `@relaycast/sdk` 5.0.5 (v4→v5 major), `relaycast` crate 5.0.2, `relaycast-sdk` 0.3.0, Swift relaycast 5.0.5. The v5 `agents.release` now returns an action invocation (like `agents.spawn`); the `remove_agent` MCP tool surfaces that invocation. | ||
| - The hosted engine base URL default is owned solely by the relaycast SDK. `agent-relay`, `agent-relay-broker`, and the bundled SDKs no longer hardcode a base URL — they pass `RELAYCAST_BASE_URL`/`RELAY_BASE_URL` through for self-hosting and otherwise inherit the SDK default (`cast.agentrelay.com`). The broker reaches the fleet node-control endpoint via the SDK's `node_control_ws_url` helper and only injects `RELAY_BASE_URL` into spawned agents when an override is set. |
There was a problem hiding this comment.
According to the repository style guide, we should use Breaking Changes and Migration Guidance sections when a SemVer-major change needs explicit callouts.
Since the upgrade of @relaycast/sdk from v4 to v5 is a major version bump that changes the return type of agents.release (returning an action invocation instead of a synchronous result), this breaking change should be documented under a ### Breaking Changes section rather than just ### Changed.
| - relaycast SDKs upgraded to latest: `@relaycast/sdk` 5.0.5 (v4→v5 major), `relaycast` crate 5.0.2, `relaycast-sdk` 0.3.0, Swift relaycast 5.0.5. The v5 `agents.release` now returns an action invocation (like `agents.spawn`); the `remove_agent` MCP tool surfaces that invocation. | |
| - The hosted engine base URL default is owned solely by the relaycast SDK. `agent-relay`, `agent-relay-broker`, and the bundled SDKs no longer hardcode a base URL — they pass `RELAYCAST_BASE_URL`/`RELAY_BASE_URL` through for self-hosting and otherwise inherit the SDK default (`cast.agentrelay.com`). The broker reaches the fleet node-control endpoint via the SDK's `node_control_ws_url` helper and only injects `RELAY_BASE_URL` into spawned agents when an override is set. | |
| - relaycast SDKs upgraded to latest: @relaycast/sdk 5.0.5 (v4->v5 major), relaycast crate 5.0.2, relaycast-sdk 0.3.0, Swift relaycast 5.0.5. | |
| - The hosted engine base URL default is owned solely by the relaycast SDK. agent-relay, agent-relay-broker, and the bundled SDKs no longer hardcode a base URL - they pass RELAYCAST_BASE_URL/RELAY_BASE_URL through for self-hosting and otherwise inherit the SDK default (cast.agentrelay.com). The broker reaches the fleet node-control endpoint via the SDK's node_control_ws_url helper and only injects RELAY_BASE_URL into spawned agents when an override is set. | |
| ### Breaking Changes | |
| - SDKs / MCP: @relaycast/sdk v5 major upgrade. agents.release now returns an action invocation (matching agents.spawn shape) instead of a synchronous result. The remove_agent MCP tool has been updated to surface this invocation. |
References
- Use Keep a Changelog sections (Added, Changed, Deprecated, Removed, Fixed, Security), plus Breaking Changes and Migration Guidance when a SemVer-major change needs explicit callouts. (link)
Resolves the relaycast git dependency lockfile to tag 5.0.5, matching the Package.swift constraint bump. swift build + swift test (70 tests) pass against 5.0.5. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
CHANGELOG.md (1)
12-12: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winSplit and shorten this changelog entry.
Line 12 packs multiple changes into one long bullet and includes implementation detail/version inventory, which makes
[Unreleased]harder to scan.Suggested rewrite
-- relaycast SDKs upgraded to latest: `@relaycast/sdk` 5.0.5 (v4→v5 major), `relaycast` crate 5.0.2, `relaycast-sdk` 0.3.0, Swift relaycast 5.0.5. The v5 `agents.release` now returns an action invocation (like `agents.spawn`); the `remove_agent` MCP tool surfaces that invocation. +- Relaycast SDKs were upgraded to v5-compatible releases across the CLI, SDK, broker, Python, and Swift packages. +- `remove_agent` now returns the release invocation payload.As per coding guidelines,
CHANGELOG.mdentries should be concise and impact-first, with one short bullet per user-visible change, and should omit implementation details.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@CHANGELOG.md` at line 12, Split the long CHANGELOG entry into multiple short, impact-first bullets under the Unreleased section instead of one inventory-style sentence. Keep the focus on user-visible changes by separating the SDK upgrade note from the agents.release/remove_agent behavior change, and remove implementation details and version listings from the changelog. Use the existing CHANGELOG.md entry as the target for the rewrite.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@CHANGELOG.md`:
- Line 12: Split the long CHANGELOG entry into multiple short, impact-first
bullets under the Unreleased section instead of one inventory-style sentence.
Keep the focus on user-visible changes by separating the SDK upgrade note from
the agents.release/remove_agent behavior change, and remove implementation
details and version listings from the changelog. Use the existing CHANGELOG.md
entry as the target for the rewrite.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 83f29477-fd4d-4518-89e6-0ecfef4ab369
⛔ Files ignored due to path filters (2)
Cargo.lockis excluded by!**/*.lockpackage-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (8)
CHANGELOG.mdcrates/broker/Cargo.tomlpackages/cli/package.jsonpackages/cli/src/cli/agent-relay-mcp.tspackages/sdk-py/pyproject.tomlpackages/sdk-swift/Package.resolvedpackages/sdk-swift/Package.swiftpackages/sdk/package.json
1 participant
Upgrades every relaycast SDK dependency to its latest published version.
Version bumps
@relaycast/sdk(packages/sdk,packages/cli)^4.1.6^5.0.5(v4→v5 major)relaycastcrate (crates/broker)=5.0.1=5.0.2relaycast-sdk(packages/sdk-py, communicate + dev)>=0.2.0>=0.3.0relaycastgit dep (packages/sdk-swift)4.2.05.0.5Lockfiles:
package-lock.jsonregenerated (npm install);Cargo.lockbumped relaycast 5.0.1→5.0.2;packages/sdk-swift/Package.resolvedresolved to tag 5.0.5.packages/sdk-py/uv.lockintentionally not touched —main's lock is already stale against its ownpyproject(re-resolving pulls ~32 unrelated transitive bumps), so that drift is left to a dedicated lock-refresh;relaycast-sdk 0.3.0resolves cleanly against the bumped constraint.v4→v5 code adaptation (TS)
The v5
@relaycast/sdkreworked agent release to flow through the action-invocation pipeline (consistent with the node-only delivery migration #1201):relay.agents.release(...)returned a synchronous result{ name, removed, deleted, reason }.relay.agents.release(...)returns an action invocation — same shape asagents.spawn({ invocationId, actionName, handlerAgentId, handlerNodeId, dispatchedNodeId?, input, status, createdAt }).packages/cli/src/cli/agent-relay-mcp.ts— theremove_agentMCP tool read the removedname/released/deleted/reasonfields, breakingtsc. Updated to surface the invocation ({ invocation }with the permissivejsonResultoutput schema), mirroring the existingspawntool.All other relay imports (
RelayCast,RelayError,RelayErrorCode,AgentClientOptions,RelayCastOptions,SDK_VERSION,WsClient,AgentClient) are unchanged in v5. The Rust 5.0.1→5.0.2 patch and the Swift 5.0.5 API needed no code changes.Per-ecosystem verification (local)
cargo build -p agent-relay-broker✅ ·cargo test -p agent-relay-broker✅ 791 + 12 + 1 passed, 0 failed ·cargo clippy -p agent-relay-broker✅ clean.tscbuild ✅ (fixed the v5 breakage above) · broker integration tests typecheck ✅ ·vitest run✅ 969 passed, 5 skipped, 0 failed (79 files). (The repo-widenpm testglob also sweeps the Swift.build/checkouts/relaycastvendored checkout's own tests; excluding that path — which CI does, since the Swift checkout isn't populated on Linux CI — relay's own suite is fully green.)relaycast-sdk 0.3.0resolves;pytest✅ 279 passed (incl. all communicate/relaycast transport tests). 4 pre-existing failures (test_dry_run,test_relay_lifecycle_hooks) are a relay-sourcesessionIdpayload mismatch onmain— reproduced identically with relaycast-sdk 0.2.0, so unrelated to this bump.swift build✅ against tag 5.0.5 ·swift test✅ 70 tests, 0 failures.🤖 Generated with Claude Code