Update uvicorn to 0.48.0

[pyup-bot]

This PR updates uvicorn from 0.4.6 to 0.48.0.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

• PyPI: https://pypi.org/project/uvicorn

Summary by CodeRabbit

• Chores
  • Updated the application's web server dependency to a significantly newer stable version. This substantial update brings performance optimizations, enhanced security patches, critical bug fixes, and improved infrastructure stability, ensuring the application operates more reliably, securely, and efficiently.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the uvicorn ASGI web server dependency in src/requirements.txt from version 0.4.6 to 0.48.0. This is a major version bump to a significantly newer release of the server runtime.

Changes

Uvicorn Dependency Update

Layer / File(s)	Summary
Uvicorn version bump src/requirements.txt	Uvicorn pinned dependency is updated from 0.4.6 to 0.48.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop and a bound through the version tree,
From point-four-six to point-forty-eight, you see!
Fresh ASGI winds now blow through the code,
Uvicorn speeds up the web server's road! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update uvicorn to 0.48.0' directly and clearly summarizes the main change - updating a dependency to a specific version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch pyup-update-uvicorn-0.4.6-to-0.48.0

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/requirements.txt`:
- Line 3: The requirements upgrade bumps uvicorn to uvicorn==0.48.0 while
fastapi stays at fastapi==0.6.4 — validate compatibility before merging by
running the provided PyPI metadata checks (or similar) to compare
requires_python and requires_dist for uvicorn and fastapi, inspect transitive
pins for fastapi (especially Starlette and Pydantic), and ensure the project
Python runtime satisfies both; if conflicts are found either downgrade/cap
uvicorn to a compatible range or perform a coordinated framework upgrade of
fastapi (and related Starlette/Pydantic) so uvicorn==0.48.0 is safe to use.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e8cb94be-7137-4f6a-826a-0b963a297647

📥 Commits

Reviewing files that changed from the base of the PR and between d377ad0 and be6fcec.

📒 Files selected for processing (1)

• src/requirements.txt

[coderabbitai]

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

Validate framework/server compatibility before merging this major jump.

uvicorn moved from 0.4.6 to 0.48.0 while fastapi remains at 0.6.4 (very old). This upgrade should be gated on explicit compatibility verification (Python range, Starlette/FastAPI interplay), otherwise startup/runtime regressions are likely.

#!/bin/bash
set -euo pipefail

# Read-only verification using PyPI metadata (no repo files required).
python - <<'PY'
import json, urllib.request

def pypi(pkg, ver):
    url = f"https://pypi.org/pypi/{pkg}/{ver}/json"
    with urllib.request.urlopen(url, timeout=20) as r:
        return json.load(r)

targets = [("uvicorn","0.48.0"), ("fastapi","0.6.4")]
for pkg, ver in targets:
    data = pypi(pkg, ver)
    info = data["info"]
    print(f"\n{pkg}=={ver}")
    print("  requires_python:", info.get("requires_python"))
    reqs = info.get("requires_dist") or []
    print("  requires_dist (first 20):")
    for r in reqs[:20]:
        print("   -", r)

print("\nInterpretation checklist:")
print("1) Ensure project Python version satisfies both requires_python constraints.")
print("2) Inspect fastapi==0.6.4 transitive pins (esp. Starlette/Pydantic).")
print("3) If constraints conflict with uvicorn==0.48.0, do a coordinated framework upgrade or cap uvicorn.")
PY

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/requirements.txt` at line 3, The requirements upgrade bumps uvicorn to
uvicorn==0.48.0 while fastapi stays at fastapi==0.6.4 — validate compatibility
before merging by running the provided PyPI metadata checks (or similar) to
compare requires_python and requires_dist for uvicorn and fastapi, inspect
transitive pins for fastapi (especially Starlette and Pydantic), and ensure the
project Python runtime satisfies both; if conflicts are found either
downgrade/cap uvicorn to a compatible range or perform a coordinated framework
upgrade of fastapi (and related Starlette/Pydantic) so uvicorn==0.48.0 is safe
to use.

[pyup-bot]

Closing this in favor of #579