LCORE-1062: updated LiteLLM deps

[tisnik]

Description

LCORE-1062: updated LiteLLM deps

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Tools used to create PR

• Assisted-by: N/A
• Generated by: N/A

Related Tickets & Documents

• Related Issue #LCORE-1062

Summary by CodeRabbit

• Chores
  • Updated litellm to version 1.80.11
  • Updated pyparsing to version 3.3.1

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated dependency versions in platform-specific requirements files: litellm from 1.80.10 to 1.80.11 and pyparsing from 3.2.5 to 3.3.1, with corresponding hash updates for each dependency.

Changes

Cohort / File(s)	Summary
Dependency version updates requirements.aarch64.txt, requirements.x86_64.txt	Updated litellm to 1.80.11 and pyparsing to 3.3.1 with new SHA256 hashes for both dependencies

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• LCORE-1062: Dependencies update #938: Updates the same dependency lockfiles with changes to pyparsing and other package hashes.
• LCORE-1026: Update dependencies #899: Modifies the same requirements files to bump the litellm package.
• LCORE-1062: updated deps #911: Updates the same requirements files and modifies the litellm dependency version.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'LCORE-1062: updated LiteLLM deps' accurately describes the main change—updating LiteLLM-related dependencies in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2fa09be and 662575a.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• requirements.aarch64.txt
• requirements.x86_64.txt

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-08-18T10:57:39.266Z

Learnt from: matysek
Repo: lightspeed-core/lightspeed-stack PR: 292
File: pyproject.toml:59-59
Timestamp: 2025-08-18T10:57:39.266Z
Learning: In the lightspeed-stack project, transitive dependencies like faiss-cpu are intentionally pinned as top-level dependencies to maintain better control over the dependency graph and avoid version conflicts when bundling ML/LLM tooling packages.

Applied to files:

• requirements.x86_64.txt
• requirements.aarch64.txt

📚 Learning: 2025-08-18T10:58:14.951Z

Learnt from: matysek
Repo: lightspeed-core/lightspeed-stack PR: 292
File: pyproject.toml:47-47
Timestamp: 2025-08-18T10:58:14.951Z
Learning: psycopg2-binary is required by some llama-stack providers in the lightspeed-stack project, so it cannot be replaced with psycopg v3 or moved to optional dependencies without breaking llama-stack functionality.

Applied to files:

• requirements.x86_64.txt
• requirements.aarch64.txt

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)

• GitHub Check: build-pr
• GitHub Check: E2E: server mode / vertexai
• GitHub Check: E2E: server mode / ci
• GitHub Check: E2E: library mode / vertexai
• GitHub Check: E2E: library mode / ci
• GitHub Check: E2E: library mode / azure
• GitHub Check: E2E: server mode / azure
• GitHub Check: Konflux kflux-prd-rh02 / lightspeed-stack-on-pull-request

🔇 Additional comments (4)

requirements.aarch64.txt (2)

1392-1394: litellm patch bump looks fine; ensure cross‑file consistency

Bumping litellm to 1.80.11 with updated hashes is reasonable and localized here. Please just double‑check:

• requirements.x86_64.txt (and any other platform‑specific lockfiles) also reference litellm==1.80.11.
• This version matches what’s expected from pyproject.toml / uv lock generation.

---

2767-2769: pyparsing patch bump looks fine; verify it matches other envs

Updating pyparsing to 3.3.1 with new hashes is a straightforward patch bump. To avoid drift, please confirm:

• Other compiled requirements (e.g., requirements.x86_64.txt) are also at pyparsing==3.3.1.
• There are no known incompatibilities with matplotlib or any parser‑related code paths in this repo for this version.

requirements.x86_64.txt (2)

1392-1394: LiteLLM bump and hashes look consistent with upstream metadata

litellm is correctly bumped to 1.80.11, and the two SHA256 hashes are well‑formed and consistent with normal uv pip compile output. The change aligns with the project’s pattern of tightly pinning LLM stack dependencies. Based on learnings, this is in line with how you manage ML/LLM tooling pins.

Please double‑check:

• That this exact version is what you’re deploying elsewhere in the stack (Docker/tag, server side), and
• That smoke tests for the LiteLLM integration (routing, logging, guardrails) pass under your typical load profile for both x86_64 and aarch64 builds.

---

2767-2769: pyparsing upgrade and hashes match PyPI; just confirm runtime compatibility

pyparsing is cleanly bumped to 3.3.1, and the pinned hashes match the wheel and sdist hashes published on PyPI for that version. (pypi.org)

Since 3.3.1 was just published, please:

• Run your parsing‑heavy tests (e.g., any matplotlib- or config‑parsing paths that rely on pyparsing) in CI or a lower environment, and
• Confirm there are no deprecation/runtime warnings or behavior changes versus 3.2.5 in your key workloads.

---

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.}