chore: update proton ref and regenerate proto

[whoAbhishekSah]

Summary

• Update PROTON_COMMIT to 3b6b44c (latest proton main) and regenerate proto

Includes proton changes:

• 3b6b44c — refactor(frontier): move SearchOrganizationTokens to FrontierService
• 0a6c0b4 — refactor(frontier): remove AddOrganizationUsers RPC
• 432d98c — feat(frontier): add RemoveOrganizationMember RPC

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
frontier	Ready	Preview, Comment	Apr 22, 2026 8:47am

[coderabbitai]

Warning

Rate limit exceeded

@whoAbhishekSah has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 19 minutes and 56 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 19 minutes and 56 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ad3e169c-4e6f-4484-966f-c858c48d695c

📥 Commits

Reviewing files that changed from the base of the PR and between 657995d and 216f6a5.

⛔ Files ignored due to path filters (4)

• proto/v1beta1/admin.pb.go is excluded by !**/*.pb.go, !proto/**
• proto/v1beta1/frontier.pb.go is excluded by !**/*.pb.go, !proto/**
• proto/v1beta1/frontierv1beta1connect/admin.connect.go is excluded by !proto/**
• proto/v1beta1/frontierv1beta1connect/frontier.connect.go is excluded by !proto/**

📒 Files selected for processing (1)

• Makefile

📝 Walkthrough

Walkthrough

The PROTON_COMMIT variable in the Makefile was updated to a new commit hash, changing which Proton archive version is fetched during proto generation.

Changes

Cohort / File(s)	Summary
Proton Commit Update Makefile	Updated PROTON_COMMIT variable from 6cf988b493611e79377362203eb7782ed19ee5c2 to 0a6c0b4f88e61524aea9d476922fa9b39995a106.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• refactor(proto): regenerate protos after gateway annotations removed #1436: Updates PROTON_COMMIT variable to point to a different Proton archive version for proto generation.
• fix: update GetBillingAccount rpc across clients #1505: Modifies the PROTON_COMMIT value in Makefile to fetch a different Proton archive.
• chore: update proton #1515: Updates Proton dependency by bumping PROTON_COMMIT and adjusting code for changed types in the new version.

Suggested reviewers

• rsbh
• rohanchkrabrty
• rohilsurana

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[coveralls]

Coverage Report for CI Build 24769124220

Coverage remained the same at 42.228%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	36895
Covered Lines:	15580
Line Coverage:	42.23%
Coverage Strength:	11.92 hits per line

---

💛 - Coveralls