feat: updated to python 3.13 and uv 5.1

[TeKrop]

Summary by Sourcery

Update the project to require Python 3.13 and upgrade uv to version 5.1. Adjust the Dockerfile and CI workflows to reflect these changes.

New Features:

• Update project to require Python 3.13.

Enhancements:

• Upgrade uv version to 5.1.

Build:

• Update Dockerfile to use Python 3.13 and uv 5.1.

CI:

• Update CI workflow to test against Python 3.13 and uv 5.1.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the project's Python version from 3.12 to 3.13 and upgrades the uv package manager from version 0.4.27 to 0.5.1. The changes are implemented through version updates in configuration files, including dependency updates and build settings modifications.

Class diagram for updated project dependencies

classDiagram
    class Project {
        +string name
        +string version
        +string description
        +string license
        +list authors
        +string readme
        +string requires-python
        +list dependencies
        +list dev-dependencies
    }
    note for Project "Updated Python version to 3.13 and pytest-cov to 6.0.*"
    Project : +dependencies = fastapi[standard]==0.115.*, httpx[http2]==0.27.*
    Project : +dev-dependencies = ipdb==0.13.*, pytest==8.3.*, pytest-asyncio==0.24.*, pytest-cov==6.0.*, pytest-randomly==3.16.*, pytest-xdist==3.6.*, ruff==0.7.*

Loading

File-Level Changes

Change	Details	Files
Updated Python version requirement from 3.12 to 3.13	Updated requires-python field to >=3.13 Changed Ruff target version to py313 Updated GitHub Actions workflow to use Python 3.13 Modified Dockerfile to use Python 3.13 base image	pyproject.toml .github/workflows/build.yml Dockerfile
Upgraded uv package manager version from 0.4.27 to 0.5.1	Updated uv version in GitHub Actions workflow Updated uv version in Dockerfile	.github/workflows/build.yml Dockerfile
Updated project version and dependencies	Bumped project version from 3.3.0 to 3.4.0 Upgraded pytest-cov from 5.0.* to 6.0.*	pyproject.toml

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sourcery-ai]

Hey @TeKrop - I've reviewed your changes - here's some feedback:

Overall Comments:

• Using Python 3.13 in production is not recommended as it's still in development. Consider using the latest stable Python 3.12.x version instead.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}