release: 1.0.0-beta.9 (install hotfix: recreate stale 3.14 venv)#1296
Conversation
…-install) A re-install over a .venv built with Python 3.14 reused it and failed the requires-python <3.14 check. The installer now probes an existing venv and recreates it with a supported 3.11-3.13 interpreter when it is out of range. Patch promotion to master so the live installer self-heals. beta.9.
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
👋 Thanks for the PR! This one targets See CONTRIBUTING.md for the branch model. |
|
Warning Review limit reached
More reviews will be available in 7 minutes and 34 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (6)
✨ 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 |
|
Note Your trial team has used its Gitar budget, so automatic reviews are paused. Upgrade now to unlock full capacity. Comment "Gitar review" to trigger a review manually. Code Review ✅ ApprovedUpdates the installer to detect and recreate stale Python 3.14 virtual environments, resolving the version mismatch issue during fresh installs. No issues found. OptionsDisplay: compact → Showing less information. Comment with these commands to change:
Important Your trial ends in 5 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
1 participant
Third install hotfix, completing the WSL fresh-install chain. Jay's re-install (Python 3.14.4) got past beta.8's requires-python cap but failed:
The beta.8 interpreter-selection only runs when CREATING a fresh venv; an existing 3.14
.venv(from an earlier attempt) was reused. Now the installer detects an out-of-range venv interpreter and recreates it. Same fix on dev via #1295.Workaround meanwhile:
sudo rm -rf <install>/.venvthen re-run the installer.Once green: merge + tag v1.0.0-beta.9 + GitHub release.