Skip to content

fix(deps): cap python version to 3.12 since 3.13 is untested in CI#616

Open
pavsoss wants to merge 1 commit into
sreerevanth:mainfrom
pavsoss:issue-599-requires-python
Open

fix(deps): cap python version to 3.12 since 3.13 is untested in CI#616
pavsoss wants to merge 1 commit into
sreerevanth:mainfrom
pavsoss:issue-599-requires-python

Conversation

@pavsoss

@pavsoss pavsoss commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Closes #599

This PR addresses the metadata over-promising support for Python 3.13/3.14 when the CI matrix only tests 3.12.

  • Updated pyproject.toml: Capped requires-python to ">=3.12,<3.13" to accurately reflect our tested matrix and prevent users from discovering edge cases on modern Python versions the hard way.
  • Updated docs/developer_setup.md: Made it explicit to contributors that they should use exactly Python 3.12 for local validation since newer versions are not yet verified in CI.

@vercel

vercel Bot commented Jul 12, 2026

Copy link
Copy Markdown

@pavsoss is attempting to deploy a commit to the sreerevanth's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 42 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a1c858ac-a42e-4681-8f2d-e23ee4700563

📥 Commits

Reviewing files that changed from the base of the PR and between a492da5 and ea3618f.

📒 Files selected for processing (2)
  • docs/developer_setup.md
  • pyproject.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@github-actions

Copy link
Copy Markdown
Contributor

🧪 PR Test Results

Check Result
Tests (pytest tests/) ✅ success
Lint (ruff check .) ❌ failure
Coverage (agentwatch) 74.19%

Python 3.12 · commit ea3618f

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.

[BUG] requires-python claims >=3.12 but CI only tests one version

1 participant