Update Python

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
python (source)	requires-python	minor	>=3.13,<3.14 → >=3.14,<3.15
python	uses-with	minor	3.13 → 3.14
python (source)	final	minor	3.13-slim-bookworm → 3.14-slim-bookworm
python (source)	stage	minor	3.13-slim-bookworm → 3.14-slim-bookworm

---

Release Notes

python/cpython (python)

v3.14.7

Compare Source

v3.14.6

Compare Source

v3.14.5

Compare Source

v3.14.4

Compare Source

v3.14.3

Compare Source

v3.14.2

Compare Source

v3.14.1

Compare Source

v3.14.0

Compare Source

actions/python-versions (python)

v3.14.7: 3.14.7

Compare Source

Python 3.14.7

v3.14.6: 3.14.6

Compare Source

Python 3.14.6

v3.14.5: 3.14.5

Compare Source

Python 3.14.5

v3.14.4: 3.14.4

Compare Source

Python 3.14.4

v3.14.3: 3.14.3

Compare Source

Python 3.14.3

v3.14.2: 3.14.2

Compare Source

Python 3.14.2

v3.14.1: 3.14.1

Compare Source

Python 3.14.1

v3.14.0: 3.14.0

Compare Source

Python 3.14.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[tobydoescode]

@renovatebot rebase

[tobydoescode]

Investigation: what actually blocks 3.14

Worked through this locally against the branch. There are three failures stacked behind each other, and the last one has no fix available to us.

1. uvloop build failure — solvable

The CI failure on this PR:

uvloop ... configure: error: C compiler cannot create executables
ERROR: process "/bin/sh -c uv sync --frozen --no-dev --no-install-project" did not complete successfully: exit code: 1

uvloop 0.21.0 (what the lock pins) has no cp314 wheel, so uv falls back to the sdist. The builder stage installs gcc but --no-install-recommends drops libc6-dev, so the compiler can't link — hence "cannot create executables".

uvloop 0.22.1 ships cp314 manylinux wheels for both arches, so re-locking clears this. With that bump the image builds cleanly on 3.14, both amd64 and arm64.

2. Slow pydantic schema construction — mitigable, not the blocker

Import is pathologically slow on 3.14: litellm/types/llms/oci.py:294 spends its time in typing.py __subclasscheck__ / abc.__subclasscheck__ while pydantic builds the model schema. 33.7s for that one submodule with pydantic 2.12.5, halved to 14.7s by 2.13.4.

Slow, but it does complete — not what breaks startup. Worth having anyway.

3. Prisma migrations hang — no fix available

With both bumps applied the container builds and starts, then loops forever:

litellm_proxy_extras - INFO - Running prisma migrate deploy
litellm_proxy_extras - INFO - Attempt 1 timed out
litellm_proxy_extras - INFO - Running prisma migrate deploy
litellm_proxy_extras - INFO - Attempt 2 timed out
litellm_proxy_extras - INFO - Running prisma migrate deploy

Each attempt burns 60s against a Postgres that the 3.13 image migrates in seconds. Measured 553s with no readiness — it never serves. prisma generate at build time works fine; it's specifically the runtime migration engine invocation that fails.

This sits in the startup critical path, so it fails hard rather than starting slowly. It would also blow the cluster's startupProbe budget (failureThreshold: 30 x periodSeconds: 10 = 300s).

Why there's nothing to wait for

prisma-client-py is archived — repo read-only, last push 2025-04-10, latest release 0.15.0 from 2024-08-16, 252 open issues. litellm constrains it to prisma<1.0,>=0.11.0 (extra-proxy), so no version in that range will ever support 3.14. Switching from our direct pin to litellm[extra-proxy] changes nothing — same package, same ceiling.

So 3.14 unblocks only when litellm itself moves off prisma-client-py.

Upstream 3.14 work, all open:

• feat: add Python 3.14 support BerriAI/litellm#31612 — feat: add Python 3.14 support
• fix(packaging): support Python 3.14 builds BerriAI/litellm#33120 — fix(packaging): support Python 3.14 builds
• LiteLLM Proxy fails to start on Python 3.14 due to uvloop incompatibility BerriAI/litellm#20933 — LiteLLM Proxy fails to start on Python 3.14 due to uvloop incompatibility
• [Bug]: Python 3.14 install fails because litellm-rust uses PyO3 0.23.5 BerriAI/litellm#33116 — Python 3.14 install fails because litellm-rust uses PyO3 0.23.5

Prisma replacement, both drafts and untouched since 2026-05-20:

• Phase 1: introduce SQLModel models alongside Prisma, with parity guard BerriAI/litellm#28366 — Phase 1: introduce SQLModel models alongside Prisma, with parity guard
• Big-bang: replace Prisma with SQLAlchemy + Prisma-compat shim BerriAI/litellm#28404 — Big-bang: replace Prisma with SQLAlchemy + Prisma-compat shim

#28404's own description states it is "lossy — it's not finished, and it's not safe to merge as-is", published to prove the shape rather than to land. Neither approach has been chosen between, and no maintainer has picked either up.

Recommendation

Close this. It can't be unblocked by anything on our side, and it will keep going red on every rebase. Reopen when litellm ships 3.14 support.

Keep for whenever that happens — both verified good:

• uvloop 0.22.1 (cp314 wheels)
• pydantic 2.13.4 (halves 3.14 import cost)