Skip to content

Use the SDK native proxy and Bezier next.14#24

Merged
pbc1017 merged 1 commit into
mainfrom
chore/bezier-next-14
Jul 23, 2026
Merged

Use the SDK native proxy and Bezier next.14#24
pbc1017 merged 1 commit into
mainfrom
chore/bezier-next-14

Conversation

@pbc1017

@pbc1017 pbc1017 commented Jul 23, 2026

Copy link
Copy Markdown
Member

Summary

  • replace the tutorial's direct Native Function HTTP transport with native.ProxyAPI.WriteGroupMessage
  • pin the merged public SDK commit until the next Go module tag is released
  • update the React WAM to @channel.io/bezier-react@4.0.0-next.14
  • update English, Korean, and Japanese README explanations to match the SDK-based flow

Test Plan

  • default Go proxy and checksum lookup resolve the pinned public pseudo-version
  • PATH=/Users/perry/.local/share/mise/installs/go/1.25.12/bin:$PATH make build
  • PATH=/Users/perry/.local/share/mise/installs/go/1.25.12/bin:$PATH make test
  • WAM build, format, lint, and typecheck

🤖 Generated with Codex

Replace the tutorial's direct Native Function transport with the merged SDK ProxyAPI and update the WAM to Bezier React 4.0.0-next.14.\n\nConstraint: Keep the tutorial fully SDK-based and reproducible before the next Go tag\nRejected: Keep the local HTTP adapter | duplicates transport now owned by the SDK\nConfidence: high\nScope-risk: moderate
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 40 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

Run ID: 8067abce-fb09-4401-9dac-4a03faaea176

📥 Commits

Reviewing files that changed from the base of the PR and between f76d128 and fedb7fb.

⛔ Files ignored due to path filters (2)
  • go.sum is excluded by !**/*.sum
  • wam/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (7)
  • README.ja.md
  • README.ko.md
  • README.md
  • cmd/main.go
  • go.mod
  • internal/tutorial/native_message.go
  • wam/package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bezier-next-14

Comment @coderabbitai help to get the list of available commands.

@pbc1017
pbc1017 merged commit 986935a into main Jul 23, 2026
1 check passed
@pbc1017
pbc1017 deleted the chore/bezier-next-14 branch July 23, 2026 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant