LCORE-1255: updated Konflux deps#1106
Conversation
WalkthroughPython version updated from 3.12 to 3.13 in the build requirements header. Two packages bumped: fastapi (0.128.0 → 0.128.1) and litellm (1.81.7 → 1.81.8) with corresponding hash updates. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@requirements.hashes.source.txt`:
- Around line 35-37: The requirements.hashes.source.txt was generated for Python
3.12 but your build target is Python 3.13; regenerate the hashes file using the
same tool you used originally (e.g., pip-compile / pip-tools) with
--python-version 3.13 so package hashes for entries like fastapi==0.128.1 (and
LiteLLM 1.81.8 if present) match Python 3.13; replace the old
requirements.hashes.source.txt with the newly generated file and verify
requirements-build.txt and requirements.hashes.source.txt now target the same
Python version.
| fastapi==0.128.1 \ | ||
| --hash=sha256:ce5be4fa26d4ce6f54debcc873d1fb8e0e248f5c48d7502ba6c61457ab2dc766 \ | ||
| --hash=sha256:ee82146bbf91ea5bbf2bb8629e4c6e056c4fbd997ea6068501b11b15260b50fb |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
FastAPI 0.128.1 Python 3.13 compatibility requirements
💡 Result:
For FastAPI 0.128.1 (released Feb 4, 2026), the Python runtime requirement is >=3.9, and the package explicitly includes Python 3.13 in its supported classifiers—so Python 3.13 is supported. [1][2]
Compatibility notes for Python 3.13:
- You must be on Pydantic v2: FastAPI 0.128.x removed support for
pydantic.v1, so apps still relying on Pydantic v1 compatibility shims must migrate. [3] - FastAPI depends on Starlette (and Pydantic); FastAPI’s version pinning will select a compatible Starlette—generally don’t pin Starlette separately unless you know you need to. [1][3]
Sources: [1] https://pypi.org/project/fastapi/ (metadata shows “Requires: Python >=3.9” and release history for 0.128.1) • [2] https://pypi.org/project/fastapi/ (classifiers include Python 3.13) • [3] https://fastapi.tiangolo.com/es/release-notes/ (0.128.0: dropped pydantic.v1; applies to 0.128.1 as well)
🌐 Web query:
LiteLLM 1.81.8 Python 3.13 support
💡 Result:
LiteLLM v1.81.8 (released Feb 5, 2026) declares Python 3.13 support on PyPI via its classifiers (“Python :: 3.13”) and sets Requires-Python: >=3.9, <4.0, so it should install and run on CPython 3.13. [1]
One caveat: if you’re using the proxy/FastAPI stack, older LiteLLM versions had reported Python 3.13 dependency conflicts (notably around uvicorn pins). If you hit install/runtime issues, check the proxy extra’s dependency resolution in your environment. [2]
Sources: [1] (PyPI litellm project page for v1.81.8 metadata/classifiers), [2] (LiteLLM GitHub issue about Python 3.13 + uvicorn conflict).
🏁 Script executed:
# Check the header of the requirements file to understand current Python version target
head -5 requirements.hashes.source.txt
# Verify if there are other Python 3.13 references in the repo
fd --type f '\.py$|\.txt$|\.toml$|\.yml$|\.yaml$|\.md$' | head -20 | xargs grep -l "3\.13" 2>/dev/null | head -10Repository: lightspeed-core/lightspeed-stack
Length of output: 354
🏁 Script executed:
# Search for Python 3.13 references in the repo
rg "3\.13" --type py --type txt --type toml --type yml --type yaml --max-count 20
# Also check for any migration or Python version update notes
rg -i "python.*3\.13|migrate|upgrade" --type md --max-count 20
# Check the requirements.source.txt (source of truth) to see what versions are being compiled
head -30 requirements.source.txtRepository: lightspeed-core/lightspeed-stack
Length of output: 870
🏁 Script executed:
# Find the actual requirements files
fd "requirements" --type f
# Check the actual requirements.source.txt or similar
fd "requirements.*" --type f -exec head -5 {} +Repository: lightspeed-core/lightspeed-stack
Length of output: 492
🏁 Script executed:
# Check the header and first 30 lines of each requirements file
echo "=== requirements.hashes.source.txt ===" && head -30 requirements.hashes.source.txt
echo -e "\n=== requirements-build.txt ===" && head -30 requirements-build.txt
echo -e "\n=== requirements.hermetic.txt ===" && head -30 requirements.hermetic.txtRepository: lightspeed-core/lightspeed-stack
Length of output: 2695
Confirm regeneration of hashes with Python 3.13 for consistency.
FastAPI 0.128.1 and LiteLLM 1.81.8 both explicitly support Python 3.13 per their PyPI classifiers. However, requirements.hashes.source.txt was compiled with --python-version 3.12, while requirements-build.txt targets Python 3.13. If Python 3.13 is now the primary build target, regenerate the hashes file with --python-version 3.13 to maintain consistency across the dependency toolchain and align with the build requirements.
🤖 Prompt for AI Agents
In `@requirements.hashes.source.txt` around lines 35 - 37, The
requirements.hashes.source.txt was generated for Python 3.12 but your build
target is Python 3.13; regenerate the hashes file using the same tool you used
originally (e.g., pip-compile / pip-tools) with --python-version 3.13 so package
hashes for entries like fastapi==0.128.1 (and LiteLLM 1.81.8 if present) match
Python 3.13; replace the old requirements.hashes.source.txt with the newly
generated file and verify requirements-build.txt and
requirements.hashes.source.txt now target the same Python version.
1 participant
Description
LCORE-1255: updated Konflux deps
Type of change
Tools used to create PR
Related Tickets & Documents
Summary by CodeRabbit