chore: bump relaycast to latest (broker crate 4.1.1 + CLI SDK 4.1.6)#1180
Conversation
Align the Rust broker's bundled `relaycast` crate with the `@relaycast/sdk` 4.x line already used by the CLI/SDK. relaycast 4.x changes its durable-delivery database schema. No broker code changes were required — the 3->4 API surface the broker consumes is unchanged; build, clippy, and the broker test suite pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughRelaycast crate and SDK dependencies are upgraded across the project. The broker's Changesrelaycast ecosystem version alignment across broker and SDK
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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.
Inline comments:
In `@CHANGELOG.md`:
- Line 36: The changelog entry for agent-relay-broker at line 36 includes
internal implementation details about "aligning the broker with the
`@relaycast/sdk` 4.x durable-delivery model" that should be removed per coding
guidelines. Simplify the entry by removing the internal reasoning phrase and
keeping only the essential information about the version upgrade (relaycast from
3.0 to 4.1) and its impact (schema change to the relaycast-backed local delivery
store), making the entry concise and impact-first as per the guidelines.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 6c6593c4-9a2a-4912-80e8-b046034ad6ef
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
CHANGELOG.mdcrates/broker/Cargo.toml
Bump the `@relaycast/sdk` dependency to the latest 4.1.x patch (4.1.2 -> 4.1.6) in `agent-relay` and `@agent-relay/sdk` so the CLI resolves a single, current 4.1.6 across its direct and workspace-transitive paths. Build, typecheck, and the SDK (110) + CLI (374) test suites pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Drop the 'aligning the broker with the @relaycast/sdk 4.x durable-delivery model' reasoning per the impact-first changelog guideline; keep the version upgrade (3.0 -> 4.1) and its impact (delivery-store schema change). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Aligns the relaycast dependency to the latest across the broker and the CLI/SDK.
Rust broker crate:
relaycast=3.0.0→=4.1.1Matches the
@relaycast/sdk4.x line. relaycast 4.x adopts the new durable-delivery model and changes its underlying delivery-store DB schema (internal to the crate — no in-repo schema/migrations).cargo build/cargo clippyclean;cargo test -p agent-relay-broker --lib→ 775 passed, 0 failed.JS SDK:
@relaycast/sdk^4.1.2→^4.1.6(latest patch)Bumped in
agent-relay(CLI) and@agent-relay/sdkso the CLI resolves a single current 4.1.6 across its direct and workspace-transitive paths.build:sdk/build:cliclean, CLItsc --noEmitclean.Note (runtime): because relaycast 4.x changes its delivery-store schema, existing local broker state written by 3.x may not be forward-compatible. No in-repo migration was added — flagging for a clear-state/migration decision if needed.