build(packaging): raise jinja2 floor to 3.1.6#27552
Conversation
Our `uv.lock` already resolves jinja2 to 3.1.6, so Docker / CI installs get that version. The `pyproject.toml` floor was lagging at 3.1.0, which means downstream consumers using `--resolution=lowest-direct` or older constraint files can land on 3.1.0-3.1.5 instead of the version we actually test against. Aligns the declared floor with the resolved version so external installers see the same baseline our test matrix exercises. `uv lock` diff is metadata-only (no resolved-version drift).
Greptile SummaryThis PR tightens the declared Jinja2 minimum version from
Confidence Score: 5/5Safe to merge — a narrowing of an existing version range with no resolved-version drift. Both changed lines are metadata-only: the floor on the Jinja2 constraint moves from 3.1.0 to 3.1.6, matching the version already resolved and tested in CI. No application logic, test coverage, or dependency graph is altered beyond tightening what installers are allowed to pick. No files require special attention.
|
| Filename | Overview |
|---|---|
| pyproject.toml | Bumps the Jinja2 minimum version from 3.1.0 to 3.1.6, aligning the declared floor with the already-resolved lockfile version. |
| uv.lock | Mirrors the pyproject.toml constraint update in the requires-dist metadata entry; no resolved version or hash changes. |
Reviews (1): Last reviewed commit: "build(packaging): raise jinja2 floor to ..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
936ada2
into
litellm_internal_staging
build(packaging): raise jinja2 floor to 3.1.6 (rc2 backport of #27552)
Summary
Bumps the declared
jinja2floor in[project.dependencies]from>=3.1.0to>=3.1.6.Our
uv.lockalready resolvesjinja2to3.1.6, so Docker images and CI installs already pick it up. Thepyproject.tomlfloor was lagging at3.1.0, which means downstream consumers using--resolution=lowest-director older constraint files can land on3.1.0–3.1.5instead of the version our test matrix exercises.This brings the declared floor in line with the resolved version so external installers see the same baseline we test against.
Scope
pyproject.toml: 1 line changed (jinja2>=3.1.0,<4.0→jinja2>=3.1.6,<4.0)uv.lock: 1 line changed (mirroredrequires-distentry; no resolved-version drift)Test plan
uv lockregenerates as a metadata-only diff — no resolved versions or hashes changelitellm_1.84.0rc2in a separate PR after merge