chore: bump NUTWATCH_REF default from v1.0.1 to v1.1.0 - #39
Conversation
Update the pinned NutWatch release tag to v1.1.0 across all install paths (VM script, standalone setup script, and documentation). v1.1.0 is now the latest published GitHub release, so new deployments should use it by default instead of the outdated v1.0.1.
|
Warning Review limit reached
More reviews will be available in 26 minutes and 51 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 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 |
2 participants
Update the pinned NutWatch release tag to v1.1.0 across all install paths (VM script, standalone setup script, and documentation). v1.1.0 is now the latest published GitHub release, so new deployments should use it by default instead of the outdated v1.0.1.