Skip to content

docs: normalize legacy plan names to current tiers#22

Merged
karlwaldman merged 1 commit into
mainfrom
chore/plan-name-normalization
Jun 21, 2026
Merged

docs: normalize legacy plan names to current tiers#22
karlwaldman merged 1 commit into
mainfrom
chore/plan-name-normalization

Conversation

@karlwaldman

Copy link
Copy Markdown
Member

Replaces the legacy Reservoir Mastery tier name in streaming-related docs, comments, the example, and the WebSocket subscription-rejected error message with current billing language.

Streaming / WebSocket gates at Professional plan ($99/mo) or higher per GET /billing/plans.

Changes

  • README.md — streaming section availability line.
  • examples/streaming.ts — header comment.
  • src/client.tsstream resource doc comment.
  • src/resources/streaming.ts — module doc comment, rig-count comment, and the runtime reject_subscription error message string.
  • tests/resources/streaming.test.ts — updated the assertion regex (/Reservoir Mastery//Professional plan/) to match the new error string.

Comments/strings only; no functional code paths changed. npm run build passes; streaming test suite passes (17/17). No version bump.

🤖 Generated with Claude Code

Replace the legacy "Reservoir Mastery (Professional+)" tier name in
streaming docs, comments, the example, and the subscription-rejected
error message with current billing language: "Professional plan
($99/mo) or higher" (WebSocket/streaming gates at Professional+).
Updated the streaming test assertion to match the new error string.
No functional code paths changed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

More reviews will be available in 20 minutes and 7 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: c84069d1-00ba-4c8e-bafc-03d3482ca159

📥 Commits

Reviewing files that changed from the base of the PR and between 764b099 and a4862a2.

📒 Files selected for processing (5)
  • README.md
  • examples/streaming.ts
  • src/client.ts
  • src/resources/streaming.ts
  • tests/resources/streaming.test.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/plan-name-normalization

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

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

@karlwaldman karlwaldman merged commit 6487f43 into main Jun 21, 2026
4 of 5 checks passed
@karlwaldman karlwaldman deleted the chore/plan-name-normalization branch June 21, 2026 17:27
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