docs: separate the 0.3.0 changelog entry from 0.4.0 - #11
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 1 hour, 21 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 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. Comment |
The spec-compliance work shipped as 0.3.0 but its notes stayed folded into the 0.4.0 section. Restore a dedicated 0.3.0 entry with the content released at the time, and scope 0.4.0 to the authorizer redesign and per-request OAuth resolution. Add the 0.4.0/0.3.0 comparison links. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Key Changes:
## [0.3.0] - 2026-06-08section inCHANGELOG.mdcontaining the spec-compliance work exactly as it shipped at the v0.3.0 release (its notes had been folded into the 0.4.0 section).## [0.4.0]section to the changes that are actually new in 0.4.0: the pluggable authorizer redesign and per-request OAuth authorization-server / protected-resource-metadata resolution.[0.4.0]and[0.3.0]comparison links at the bottom.Testing:
Other: