Skip to content

Update and lock all dependencies#67

Merged
5hojib merged 1 commit intobetafrom
update-dependencies-14347183005228516033
Feb 11, 2026
Merged

Update and lock all dependencies#67
5hojib merged 1 commit intobetafrom
update-dependencies-14347183005228516033

Conversation

@5hojib
Copy link
Member

@5hojib 5hojib commented Feb 11, 2026

Updated all dependencies to their latest compatible versions and locked them in uv.lock, requirements.lock, and requirements-dev.lock. Also updated pyproject.toml to reflect these updates as minimum version requirements.


PR created automatically by Jules for task 14347183005228516033 started by @5hojib

Summary by Sourcery

Update dependency version constraints and lockfiles to current compatible releases.

Enhancements:

  • Raise minimum supported versions for core runtime, development, and documentation dependencies in pyproject.toml.

Build:

  • Regenerate uv.lock, requirements.lock, and requirements-dev.lock to reflect updated dependency graph.

This commit updates top-level dependency constraints in `pyproject.toml` to their latest compatible versions and regenerates all lock files (`uv.lock`, `requirements.lock`, and `requirements-dev.lock`).

Key changes:
- Updated `pysocks`, `aiosqlite`, `pymediainfo`, `pymongo`, `ElectroCrypto`, and `anyio` minimum versions in `pyproject.toml`.
- Bumped `hatch` and `pytest` minimum versions in `dev` extra.
- Updated `sphinx` constraint to `<10.0.0` and added minimum versions for other documentation and development tools.
- Regenerated `uv.lock` with latest compatible versions.
- Re-exported `requirements.lock` and `requirements-dev.lock` with hashes using `uv export`, ensuring consistency across dependency management tools.
- Verified all tests pass in the updated environment.

Co-authored-by: 5hojib <107526130+5hojib@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Feb 11, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Refreshes and pins all Python dependencies to current compatible versions, updating pyproject minimum versions and regenerating all lockfiles for runtime, dev, and uv-based environments.

File-Level Changes

Change Details Files
Set explicit minimum versions for main runtime dependencies in pyproject.toml.
  • Replaced unpinned core runtime dependencies with version-constrained entries using >= for pysocks, aiosqlite, pymediainfo, pymongo, and ElectroCrypto.
  • Kept anyio pinned with an updated minimum compatible version constraint if necessary.
pyproject.toml
Set explicit minimum versions for development and documentation dependencies in pyproject.toml.
  • Replaced unpinned dev tools (hatch, pytest, pytest-asyncio, pytest-cov, twine) with >= minimum version constraints.
  • Relaxed and updated Sphinx constraint to <10.0.0 and added minimum versions for sphinx-immaterial, sphinx_copybutton, and tornado while keeping sphinx-autobuild.
  • Ensured optional doc dependencies reflect newer compatible releases.
pyproject.toml
Regenerated all lockfiles to match the updated dependency set.
  • Updated requirements.lock with the resolved versions of runtime dependencies and their transitive tree.
  • Updated requirements-dev.lock to reflect dev and docs dependency resolutions.
  • Updated uv.lock to capture the full dependency graph for the uv-based workflow.
requirements.lock
requirements-dev.lock
uv.lock

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @5hojib, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request comprehensively updates and locks all project dependencies, ensuring that the development and production environments utilize the most current and compatible package versions. The changes involve updating explicit minimum version requirements in pyproject.toml and regenerating the lock files (uv.lock, requirements.lock, requirements-dev.lock) to capture the exact versions and their transitive dependencies. This refresh aims to improve project reliability and maintainability by incorporating the latest bug fixes and performance enhancements from upstream packages.

Highlights

  • Dependency Updates: All project dependencies have been updated to their latest compatible versions to ensure stability and leverage new features.
  • Lock File Regeneration: The uv.lock, requirements.lock, and requirements-dev.lock files were regenerated using uv to reflect the updated dependency tree and ensure consistent installations.
  • pyproject.toml Adjustments: Minimum version requirements for core, development, and documentation dependencies in pyproject.toml were updated to align with the new dependency versions.
  • Python Version Resolution: The uv.lock file now includes more granular resolution markers for different Python full versions, specifically for docutils and sphinx.
Changelog
  • pyproject.toml
    • Updated minimum version requirements for core dependencies including pysocks, aiosqlite, pymediainfo, pymongo, and ElectroCrypto.
    • Updated minimum version requirements for development dependencies such as hatch, pytest, pytest-asyncio, pytest-cov, and twine.
    • Updated minimum version requirements for documentation dependencies like sphinx, sphinx-immaterial, sphinx_copybutton, and tornado.
  • requirements-dev.lock
    • Regenerated the lock file using uv instead of rye.
    • Updated versions and hashes for numerous development dependencies.
    • Added new development dependencies including anyio, backports-asyncio-runner, h11, httpx, hyperlink, id, iniconfig, jaraco-context, jaraco-functools, jeepney, keyring, markdown-it-py, mdurl, more-itertools, nh3, packaging, pathspec, pexpect, platformdirs, pluggy, ptyprocess, pycparser, pygments, pyproject-hooks, pytest, pytest-asyncio, pytest-cov, pywin32-ctypes, readme-renderer, requests, requests-toolbelt, rfc3986, rich, secretstorage, shellingham, tomli, tomli-w, tomlkit, trove-classifiers, twine, typing-extensions, urllib3, userpath, uv, virtualenv, and zipp.
    • Removed several development dependencies such as cfgv, nodeenv, pre-commit, pyyaml, and ruff.
  • requirements.lock
    • Regenerated the lock file using uv instead of rye.
    • Updated versions and hashes for core dependencies including aiosqlite, dnspython, electrocrypto, pymediainfo, pymongo, and pysocks.
    • Added new core dependencies such as anyio, exceptiongroup, idna, and typing-extensions.
  • uv.lock
    • Updated Python version resolution markers to include python_full_version == '3.11.*' and python_full_version >= '3.12'.
    • Introduced conditional docutils package definitions based on python_full_version.
    • Updated conditional sphinx package definitions and their dependencies (sphinx-autobuild, sphinx-copybutton, sphinx-immaterial) based on python_full_version.
    • Made importlib-metadata's dependency on zipp conditional on python_full_version < '3.12'.
    • Removed the roman-numerals-py package entry.
Activity
  • PR created automatically by Jules for task 14347183005228516033, initiated by @5hojib.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • Now that minimum versions are specified, consider adding upper bounds (especially for libraries known to introduce breaking changes in major releases like pymongo and sphinx) to avoid unexpected breakage from future incompatible releases.
  • The change from sphinx<9.0.0 to sphinx<10.0.0 potentially widens the allowed major-version range; verify that the project is actually compatible with Sphinx 9.x and, if not, keep the upper bound aligned with the last known compatible major version.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Now that minimum versions are specified, consider adding upper bounds (especially for libraries known to introduce breaking changes in major releases like `pymongo` and `sphinx`) to avoid unexpected breakage from future incompatible releases.
- The change from `sphinx<9.0.0` to `sphinx<10.0.0` potentially widens the allowed major-version range; verify that the project is actually compatible with Sphinx 9.x and, if not, keep the upper bound aligned with the last known compatible major version.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates dependency management from rye to uv, leading to a complete regeneration of requirements-dev.lock and requirements.lock files, which now include SHA256 hashes for all dependencies. The pyproject.toml file has been updated to specify minimum version requirements for core, development, and documentation dependencies, including an increased upper bound for sphinx. The uv.lock file reflects these changes by introducing more granular Python version resolution markers and updating specific package versions like docutils and sphinx to support different Python environments (e.g., Python 3.11 and 3.12+), while also removing the roman-numerals-py package.

@5hojib 5hojib merged commit 7f7fb04 into beta Feb 11, 2026
2 checks passed
@5hojib 5hojib deleted the update-dependencies-14347183005228516033 branch February 11, 2026 15:14
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