chore(deps): bump @relayfile/sdk to 0.8.29

[khaliqgant]

Summary

• Bumps @relayfile/sdk from ^0.8.27 → ^0.8.29

Why

Picks up outbound webhook subscription client methods added in relayfile#281 (registerWebhook, listWebhooks, deleteWebhook, getWebhookDeadLetters, replayWebhookDeadLetter) and the WebhookSubscription / WebhookDeliveryDeadLetterItem types.

This is the SDK prerequisite for pear#347 — the factory webhook handler that makes the factory stateless.

Test plan

• npm run typecheck passes (both web + node)
• pear#347 factory webhook handler implementation (follow-on)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 44 minutes and 42 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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

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: 40bb844e-4f5b-4cc9-88a7-2970ddde4806

📥 Commits

Reviewing files that changed from the base of the PR and between 0772c7b and d8e2985.

⛔ 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 ar-267-relayfile-sdk-bump

---

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 the @relayfile/sdk dependency from version 0.8.27 to 0.8.29 in both package.json and package-lock.json, along with its associated sub-packages. I have no feedback to provide as there are no review comments or issues identified in these dependency updates.

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.

[devin-ai-integration]

✅ Devin Review: No Issues Found

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

[agent-relay-code]

Findings

No blocking issues found in the PR diff. The change is scoped to bumping @relayfile/sdk to ^0.8.29 in package.json and the matching lockfile entries. The installed package exposes the webhook client methods and types the PR description calls out.

No files were edited.

Addressed comments

• CodeRabbit: reported review rate limit only; no actionable code finding. No change made.
• Gemini Code Assist: stated no issues found with the dependency update. No change made.
• Devin Review: stated no issues found. No change made.

Validation

Local checks run:

• npm ci passed
• npm run verify:mcp-resources-drift passed
• npm run lint passed with existing warnings
• npm run typecheck:web passed
• npm run typecheck:node passed
• npm test passed
• npx vitest run passed
• npm run build passed
• npm run build:web passed
• npx playwright test --config playwright.fidelity.config.ts initially had contention-related failures; failed specs passed when rerun serially
• npx playwright test --config playwright.redraw.config.ts passed when rerun by itself

I did not run the macOS dist:mac / packaged MCP smoke job in this Linux sandbox. The GitHub connector reports PR #358 is already closed and merged, so I’m not ending with READY.