build(deps): allow redisvl, pypdf, and openapi-core on Python 3.14

[yuneng-berri]

Relevant issues

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

Screenshots / Proof of Fix

litellm already installs on Python 3.14; this change is about the optional dependencies that were still fenced off from it. The proof has two halves: nothing moves for the existing 3.10 through 3.13 range, and the three packages genuinely install and work on a real 3.14 interpreter. Because this is a packaging change, the realistic proof is a source install plus importing and exercising the features, not an LLM call; a plain pip install litellm on 3.14 additionally waits on the cp314 wheels that ship separately

Commits the proof was captured at: markers present at 966ff65fec, markers removed at 4b85239c70, native 3.14 re-verified on this branch tip 3d972c8f55 (after merging #33798 so the Rust bridge builds on 3.14)

1. No regression on Python 3.10 through 3.13. Regenerating the lock with the markers gone changed no package version on any Python branch. A name+version map of every locked package is identical before and after, and the lock diff contains no version, hash, or artifact-url change at all:

$ diff <(vmap uv.lock@966ff65fec) <(vmap uv.lock@4b85239c70)   # 420 packages each side
        (no output -> every package resolves to the same version)

$ git diff 966ff65fec..4b85239c70 -- uv.lock | grep -E '^[+-](version = |.*sha256|.*files.pythonhosted)'
        (no output -> only marker text and uv's rolling exclude-newer timestamp changed)

The same three feature suites run green before and after on 3.13.13, so the un-gated deps behave identically where they were already installed:

# 966ff65fec (markers present)
$ uv run --python 3.13 pytest \
    tests/test_litellm/caching/test_redis_semantic_cache.py \
    tests/test_litellm/interactions/test_openapi_compliance.py \
    tests/test_litellm/test_rag_openai_ingestion.py -q
56 passed in 12.08s

# 4b85239c70 (markers removed)
$ uv run --python 3.13 pytest <same three files> -q
56 passed in 7.63s

2. The three packages install and work on native Python 3.14. With #33798 merged in, a full extras sync builds and resolves on 3.14.6 with no forward-compatibility shim:

# 3d972c8f55, on python 3.14.6
$ uv sync --all-extras --python 3.14
Resolved 420 packages ... (exit 0)

$ uv run --python 3.14 pytest tests/test_litellm/interactions/test_openapi_compliance.py -q
13 passed in 1.25s
# this suite does `from openapi_core import OpenAPI` at module top, so collection
# itself fails if openapi-core is still gated out

$ uv run --python 3.14 python -c "import pypdf; \
    from litellm.rag.ingestion.file_parsers.pdf_parser import extract_text_from_pdf; \
    t=extract_text_from_pdf(open('tests/llm_translation/fixtures/dummy.pdf','rb').read()); \
    assert t and len(t)>0; print('pypdf', pypdf.__version__, '| chars', len(t), '|', repr(t.strip()))"
pypdf 6.13.3 | chars 13 | 'Test PDF File'
# real bytes through litellm's own parser, which returns nothing if pypdf is absent

$ uv run --python 3.14 python -c "import redisvl; \
    from redisvl.extensions.llmcache import SemanticCache; \
    from redisvl.utils.vectorize import CustomTextVectorizer; \
    import litellm.caching.redis_semantic_cache; print('redisvl', redisvl.__version__)"
redisvl 0.4.1

$ uv run --python 3.14 python -c "import redisvl, pypdf, openapi_core; \
    print(redisvl.__version__, pypdf.__version__, openapi_core.__version__)"
0.4.1 6.13.3 0.22.0

One honesty note on redisvl: its existing unit suite mocks the client through sys.modules, so it passes with or without the package installed; the real-import line above is what demonstrates the package is present on 3.14. A full semantic-cache round-trip additionally needs a live Redis with the RediSearch module, which is orthogonal to whether the dependency is installable

Type

🚄 Infrastructure

Changes

Three optional dependencies were still excluded on Python 3.14 by python_version < '3.14' environment markers, so the features that depend on them stayed unavailable there even after litellm itself became installable on 3.14. This removes that marker from redisvl (the Redis semantic cache, litellm/caching/redis_semantic_cache.py), pypdf (RAG PDF ingestion, litellm/rag/ingestion/file_parsers/pdf_parser.py), and openapi-core (the dev dependency behind the OpenAPI compliance tests). All three declare support for 3.14 within their pinned bands, and the regenerated lock confirms they resolve on 3.14 with no change anywhere else

semantic-router and aurelio-sdk keep their markers on purpose: every published semantic-router release still caps python_requires below 3.14, so the semantic guardrail cannot run there until upstream ships a compatible release

The lock regeneration is marker-only. redisvl stays at 0.4.1, pypdf at 6.13.3, and openapi-core at 0.22.0, each now also covering 3.14; no other package moved on any Python version. The single non-marker line in the lock diff is uv's rolling exclude-newer timestamp, which has no effect on resolution. make pre-commit and uv lock --check both pass locally

This is the Python-side half of enabling 3.14; it merges in #33798, which raised the Rust bridge's pyo3 to 0.29, so a source install now builds the native module on 3.14 as well. No new test file is added deliberately: the change is a dependency-marker removal held to the smallest reviewable diff, and it is covered by the existing feature suites run before and after on 3.13 and natively on 3.14 above, rather than a 3.14-only test that current CI has no lane to run yet

Final Attestation

• The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

[greptile-apps]

Greptile Summary

This PR removes the python_version < '3.14' environment markers from three optional dependencies — redisvl, pypdf, and openapi-core — so those features become available on Python 3.14. The lock file is regenerated to match: only marker text and uv's rolling exclude-newer timestamp changed; no package version moved on any Python branch.

• redisvl (Redis semantic cache, extra-proxy extra), pypdf (RAG PDF ingestion, proxy-runtime extra), and openapi-core (dev/test dependency) all have their Python 3.14 exclusion markers removed; semantic-router and aurelio-sdk intentionally retain their markers because upstream still caps python_requires below 3.14.
• The uv.lock changes are purely mechanical: dependency markers for transitive deps are updated to follow the three newly ungated roots, and ml_dtypes/redisvl correctly extend the numpy 2.4.4 marker from >= '3.12' and < '3.14' to >= '3.12'.

Confidence Score: 5/5

Safe to merge — purely a marker removal with no version or logic changes anywhere in the dependency graph.

The change is a two-file, marker-only edit. The lock diff confirms that no package version moved on any existing Python branch, and the PR description provides explicit resolution proof on Python 3.14. There is nothing here that could regress existing behavior.

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Removes python_version < '3.14' markers from redisvl (extra-proxy), pypdf (proxy-runtime), and openapi-core (dev); semantic-router and aurelio-sdk markers are intentionally kept
uv.lock	Lock file regenerated: markers dropped from all transitive deps of the three ungated packages; no package versions changed; only the rolling exclude-newer timestamp updated

_{Reviews (1): Last reviewed commit: "Merge remote-tracking branch 'origin/lit..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed-hq]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_/bold-brahmagupta-943951 (3d972c8) with litellm_internal_staging (f3d2015)¹}

Footnotes

1. No successful run was found on litellm_internal_staging (c725017) during the generation of this report, so f3d2015 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩