Update project dependencies

[temotskipa]

No description provided.

[qodo-code-review]

PR Summary by Qodo

Bump locked Python dependencies (uv.lock)

⚙️ Configuration changes 🕐 20-40 Minutes

AI Description

• Update uv.lock to newer upstream package versions.
• Pull in security/network stack upgrades (cryptography, certifi, websockets, uvicorn).
• Refresh developer tooling lock entries (ruff) and related transitive deps.

Diagram

graph TD
  A["Project"] --> B["uv.lock"] --> C{{"PyPI registry"}}
  B --> D["Runtime deps"] --> C
  B --> E["Dev tooling"] --> C

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Automated dependency update bot (Dependabot/Renovate)

• ➕ Regular, smaller updates reduce risk of large multi-package bumps
• ➕ Built-in changelog/security advisory context per update PR
• ➖ More PR noise/triage overhead
• ➖ May require repo-specific configuration to avoid unwanted update patterns

2. Separate PRs for major-version upgrades

• ➕ Isolates risk (e.g., websockets 16→17, cryptography 49→50) for easier rollback
• ➕ Reviewers can focus on changelog/compatibility for one major bump at a time
• ➖ Slower overall update cadence
• ➖ More branch/PR management overhead

Recommendation: Current approach (single lock refresh) is reasonable if CI covers integration paths; however, because this includes major-version upgrades (notably websockets and cryptography), consider either splitting majors into dedicated PRs or adding an automated update workflow going forward to keep changes smaller and easier to validate.

Files changed (1) +178 / -166

Other (1) +178 / -166

uv.lockRefresh locked dependency versions and artifacts +178/-166

Refresh locked dependency versions and artifacts

• Updates resolved versions, sdists, and wheel hashes/URLs for multiple Python packages in the uv lockfile. Notable bumps include cryptography 49.0.0→50.0.0, websockets 16.1→17.0.1, uvicorn 0.51.0→0.52.0, certifi 2026.6.17→2026.7.22, and ruff 0.16.0→0.16.1.

uv.lock

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 16 rules

1. uv.lock line exceeds 100 📘 Rule violation ✧ Quality

Description

The updated sdist/wheels entries in uv.lock add lines that exceed 100 characters, violating
the repository's maximum line-length requirement. This can cause lint/format checks to fail and
reduces readability.

Code

uv.lock[30]

+sdist = { url = "https://files.pythonhosted.org/packages/5f/56/a8120250d128bed162cd73c76d45f6ef9991f3e068f62a8ee060afa3104a/annotated_types-0.8.0.tar.gz", hash = "sha256:13b2beaad985e05e2d6407ee4c4f35590b11f8d693a258a561055cac8f64cab7", size = 15893, upload-time = "2026-07-23T20:16:13.995Z" }

Relevance

● Weak

uv.lock updates merged with long sdist/wheel lines; no evidence reviewers enforce 100-char limit for
lockfile.

PR-#337
PR-#311
PR-#354

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

PR Compliance ID 222796 requires that changed non-comment lines be <= 100 characters. The modified
sdist = { url = ..., hash = ..., size = ..., upload-time = ... } line in uv.lock is
substantially longer than 100 characters.

Rule 222796: Enforce maximum line length of 100 characters
uv.lock[30-30]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`uv.lock` contains newly modified lines longer than 100 characters (e.g., long inline `sdist`/`wheels` tables with URLs and hashes), violating the max line-length rule.

## Issue Context
Lockfiles are often auto-generated and may not support manual wrapping without breaking tooling. If `uv.lock` is intended to be exempt, the exception must be explicitly documented and enforced via config; otherwise, the file must be regenerated/rewritten in a wrapped format if supported.

## Fix Focus Areas
- uv.lock[30-30]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}