chore: upgrade uv and ruff

[gruebel]

This PR

• no actual changes needed

[gemini-code-assist]

Summary of Changes

Hello @gruebel, I'm Gemini Code Assist¹! 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 focuses on upgrading key development dependencies and tools to their latest versions. Specifically, it updates ruff for linting, mypy for type checking, and uv for build and dependency management. These updates ensure the project benefits from the latest features, performance improvements, and bug fixes in these tools, contributing to a more robust and efficient development workflow without introducing any functional changes to the application code itself.

Highlights

• Dependency Upgrades: The ruff-pre-commit hook has been updated from version v0.13.0 to v0.14.2.
• Dependency Upgrades: The mirrors-mypy hook has been updated from version v1.18.1 to v1.18.2.
• Dependency Upgrades: The uv_build requirement in pyproject.toml has been updated from ~=0.8.0 to ~=0.9.0.
• Dependency Upgrades: The uv required version has been updated from ~=0.8.0 to ~=0.9.0.

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. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.89%. Comparing base (0d8369f) to head (21feabf).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #545   +/-   ##
=======================================
  Coverage   97.89%   97.89%           
=======================================
  Files          39       39           
  Lines        1849     1849           
=======================================
  Hits         1810     1810           
  Misses         39       39           

Flag	Coverage Δ
unittests	97.89% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gemini-code-assist]

Code Review

This pull request upgrades the versions of uv and ruff used in the project. My review focuses on the implications of these upgrades. I've identified two areas for improvement to align the project's configuration with the new tool versions. One suggestion is to update a deprecated configuration section in pyproject.toml following the ruff upgrade. The other is to investigate simplifying the project's script handling, as the uv upgrade may render the current workaround obsolete. These changes will improve the project's maintainability.