Skip to content

Drop Python 3.8, bump all deps to latest#15

Merged
GeiserX merged 2 commits intomainfrom
deps/bump-all-deps-drop-py38
Apr 27, 2026
Merged

Drop Python 3.8, bump all deps to latest#15
GeiserX merged 2 commits intomainfrom
deps/bump-all-deps-drop-py38

Conversation

@GeiserX
Copy link
Copy Markdown
Owner

@GeiserX GeiserX commented Apr 27, 2026

Summary

  • Drop Python 3.8 (EOL since Oct 2024) from CI matrix and setup.py classifiers
  • Add Python 3.12 and 3.13 to CI matrix and classifiers
  • Bump all dependencies to latest versions across requirements.txt, requirements-dev.txt, and setup.py extras_require

Dependency changes

Package Old New
requests >=2.31.0 >=2.32.5
beautifulsoup4 >=4.12.0 >=4.14.3
lxml >=4.9.4 >=5.4.0
Pillow >=10.0.0 >=11.2.1
pytest >=7.4.4 >=8.3.5
pytest-cov >=4.1.0 >=6.2.1
pytest-mock >=3.11.0 >=3.15.1
selenium >=4.10.0 >=4.36.0
numpy >=1.24.0 >=2.2.6

Why combined

Python 3.8 EOL means numpy>=1.26.4, selenium>=4.36, pytest-mock>=3.15, and requests>=2.32.5 all dropped 3.8 support. The individual dependabot PRs (#6-#14) each fail CI on the 3.8 matrix entry. This single PR resolves all of them together.

Supersedes: #6, #7, #8, #9, #10, #11, #12, #13, #14

Test plan

  • CI passes on Python 3.9, 3.10, 3.11, 3.12, 3.13
  • All existing tests pass with bumped dependencies

Python 3.8 reached EOL in Oct 2024. Multiple dependencies
(numpy, selenium, pytest-mock, requests) have already dropped
3.8 support, causing CI failures on dependabot PRs.

- CI matrix: 3.8-3.11 -> 3.9-3.13
- setup.py: python_requires>=3.9, updated classifiers
- requirements.txt: requests 2.32.5, beautifulsoup4 4.14.3,
  lxml 5.4.0, Pillow 11.2.1
- requirements-dev.txt: pytest 8.3.5, pytest-cov 6.2.1,
  pytest-mock 3.15.1, selenium 4.36.0, numpy 2.2.6
- setup.py extras_require: aligned with requirements files
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 27, 2026

Warning

Rate limit exceeded

@GeiserX has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 52 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 180ba070-dce1-4d32-8253-63f61f5ca156

📥 Commits

Reviewing files that changed from the base of the PR and between f86d109 and c0820b0.

📒 Files selected for processing (4)
  • .github/workflows/main.yml
  • requirements-dev.txt
  • requirements.txt
  • setup.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch deps/bump-all-deps-drop-py38

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 and usage tips.

@GeiserX GeiserX merged commit 281a5cf into main Apr 27, 2026
11 checks passed
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