fix(nip33): rename info tag protocol_versions -> protocol_version#782
Conversation
Client and node are compatible only when they run the same protocol
version, so the kind-38385 info tag carries a single value ("1" or "2"),
not a list. Rename the emitted tag (and docs) to the singular form to
match the protocol spec and the mostro-cli reader.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 16 minutes and 43 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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
What
Rename the kind-38385 info-event tag
protocol_versions→protocol_version(singular), insrc/nip33.rsanddocs/TRANSPORT_V2_SPEC.md.Why
A client and a node are compatible only when they run the same protocol version, so the tag advertises a single value (
"1"or"2"), never a list. The plural name was misleading. The emitting method is already singular (transport.protocol_version()); only the tag key string changes.Coordination
Must land together with the matching changes in:
Until the daemon emits the new tag name, a CLI that reads
protocol_versionwon't auto-detect this node's transport (falls back to gift-wrap).🤖 Generated with Claude Code