Bump relay dependency packages

[miyaontherelay]

Summary

• bump Agent Relay runtime packages to the latest 9.x releases
• bump @relayfile/sdk to 0.10.9 for the latest relay property support
• keep Relayflows packages at their current latest 1.0.3
• refresh package-lock.json against the updated dependency set

Versions

• @agent-relay/cloud: ^9.0.2
• @agent-relay/harness-driver: ^9.0.2
• @agent-relay/integration-prompts: ^9.0.2
• agent-relay: ^9.0.1
• @relayfile/sdk: ^0.10.9
• @relayflows/cli: ^1.0.3 (already latest)
• @relayflows/core: ^1.0.3 (already latest)

Tests

• npm ls @agent-relay/cloud @agent-relay/harness-driver @agent-relay/integration-prompts @relayfile/sdk agent-relay @relayflows/cli @relayflows/core --depth=0
• npm run build
• npm test

[coderabbitai]

Warning

Review limit reached

@miyaontherelay, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 52 minutes and 51 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1622940c-1ef5-447e-93dc-77ef39e9e8f0

📥 Commits

Reviewing files that changed from the base of the PR and between 3d0ea41 and e63a122.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-relay-deps

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates several @agent-relay dependencies and @relayfile/sdk to their latest versions in package.json and package-lock.json. Feedback on these changes highlights that @agent-relay/fleet is imported within the codebase but is missing from the direct dependencies in package.json. It is recommended to explicitly add @agent-relay/fleet to prevent potential build or runtime failures caused by relying on transitive dependency hoisting.

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.

[gemini-code-assist]

The package directly imports from @agent-relay/fleet in multiple files (such as src/node/factory-node.ts and src/orchestrator/factory.ts), but @agent-relay/fleet is not declared as a direct dependency in package.json. Relying on transitive dependency hoisting can lead to build or runtime failures if the dependency tree changes. It should be explicitly added to the dependencies list.

Suggested change

	"@agent-relay/cloud": "^9.0.2",
	"@agent-relay/harness-driver": "^9.0.2",
	"@agent-relay/integration-prompts": "^9.0.2",
	"@relayfile/sdk": "^0.10.9",
	"agent-relay": "^9.0.1",
	"@agent-relay/cloud": "^9.0.2",
	"@agent-relay/fleet": "^9.0.2",
	"@agent-relay/harness-driver": "^9.0.2",
	"@agent-relay/integration-prompts": "^9.0.2",
	"@relayfile/sdk": "^0.10.9",
	"agent-relay": "^9.0.1",