chore: bump swap-widget to 0.5.2 and caip to 8.16.10 for next release

[kaladinlight]

Description

Version bumps to publish the two fixes that landed on develop since the last release:

• @shapeshiftoss/swap-widget 0.5.1 → 0.5.2 — picks up fix(swap-widget): raise viem peer floor to ^2.45.0 and guard empty publishes #12506 (viem peer floor raised to ^2.45.0, empty-publish guard)
• @shapeshiftoss/caip 8.16.9 → 8.16.10 — picks up fix(caip): keep Node's fs out of the browser-reachable module graph #12507 (Node's fs kept out of the browser-reachable module graph)

swap-widget externalizes its dependencies at build time, so consumers get the caip fix via the published @shapeshiftoss/caip package — hence both bumps ship together.

Issue (if applicable)

closes #

Risk

Low — version-only changes to two package.json files. Publishing happens via the existing publish-packages.yml workflow on merge to main.

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

None.

Testing

Engineering

Verify the versions aren't already on npm (npm view @shapeshiftoss/swap-widget version → 0.5.1, npm view @shapeshiftoss/caip version → 8.16.9). The publish workflow picks up both packages once this reaches main.

Operations

• 🏁 No user-facing changes; nothing to QA.

Screenshots (if applicable)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@kaladinlight, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 55db79f7-1f5d-4316-9a68-d4b7cf43e7c0

📥 Commits

Reviewing files that changed from the base of the PR and between 6b5ad20 and 16657ce.

📒 Files selected for processing (2)

• packages/caip/package.json
• packages/swap-widget/package.json

---

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.}