emdash/some-pandas-search-b3pew - #430
Conversation
test/unit/toolchain_pins_test.rb asserted .mise.toml version pins equal the literal pins in the setup-hugo action, _hugo.yml, .dev/compose.yml and .ruby-version. It tested config *agreement*, not behavior, and red-built on a false invariant: .mise.toml node="latest" (devs want latest) vs CI node-version:'22' (pinned on purpose in #393) - a correct divergence. Violates FIRST + the CLAUDE.md "no fragile config assertions" rule. Refs cleaned: Rakefile :guards list, .mise.toml / setup-hugo action.yml comments, README, docs/SETUP.md, .okf ci-gates + log. Pins now sync by convention when bumping. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 37 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
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 |
setup-node@v4 resolves 'latest' to the newest release, matching .mise.toml node="latest" so CI and local no longer diverge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
No description provided.