chore(release): v14.4.0#262
Conversation
Sync version files to the manually cut v14.4.0 release (release-please skipped the chore-only promotion squash). Bumps package.json + the release-please manifest and adds the v14.4.0 CHANGELOG section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 20 minutes and 17 seconds. Learn how PR review limits work. To continue reviewing without waiting, enable usage-based billing in the billing tab. ⌛ 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
✨ 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 |
Sync version metadata for the v14.4.0 release
The v14.4.0 GitHub Release + tag were cut manually because release-please skipped the promotion (PR #261 squash-merged as a single
chorecommit → no releasablefeat/fixfor release-please to act on). This PR brings the in-repo metadata in line so release-please stays consistent for the next cycle:package.json→ 14.4.0 (+package-lock.json).release-please-manifest.json→ 14.4.0CHANGELOG.md→ adds the v14.4.0 section (matches the GitHub Release notes)No code changes — metadata only.
🤖 Generated with Claude Code