Skip to content

v0.2.3 - #20

Merged
jayzuccarelli merged 1 commit into
mainfrom
release-v023
Jul 20, 2026
Merged

v0.2.3#20
jayzuccarelli merged 1 commit into
mainfrom
release-v023

Conversation

@jayzuccarelli

Copy link
Copy Markdown
Owner

Cuts the release so the fixes in #19 actually reach curl | bash users. install.sh resolves the newest vN.N.N tag, so nothing merged to main ships until a tag exists.

Shipping in this tag:

  • LGPL isolation. browser-cookie3 (LGPL-3.0) no longer imported into this MIT codebase; it runs in a child interpreter behind a chrome-cookies extra, with the extra wired into both uv sync sites and the uv run wrapper so the Chrome login import keeps working.
  • Usage stats are opt-in. Unset means off; setup asks once with the default set to no and records the answer in .env. Crash reports stay env-var only and are never prompted for.
  • Non-TTY runs exit cleanly instead of dumping a prompt_toolkit traceback.
  • Grammar repairs across README, CONTRIBUTING, AGENTS, CLAUDE, and the bug-report template.

Version bump only in this PR: pyproject.toml and the matching uv.lock line. 143 tests pass, ruff clean.

Ships the LGPL isolation, opt-in usage stats, and the non-TTY fix to
installs. install.sh pins the newest release tag, so none of it reaches a
`curl | bash` user until a tag exists.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jayzuccarelli, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 11639c31-16cd-42bd-ba11-6c26d71898b0

📥 Commits

Reviewing files that changed from the base of the PR and between e84df1b and 32de999.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • pyproject.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-v023

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jayzuccarelli
jayzuccarelli merged commit 6b90246 into main Jul 20, 2026
2 of 4 checks passed
@jayzuccarelli
jayzuccarelli deleted the release-v023 branch July 20, 2026 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant