chore: pin LiteLLM to known good version

[willkill07]

Description

Per internal guidance, pin LiteLLM to a known good version.

• Keeps the lower-bound specification (>=1.74)
• Effectively changes the upper-bound from (<2.0 to <1.82.7)
• Added greppable string: # pin to known-good version for easier replacement.

Although 1.82.7 and 1.82.8 have already been purged from PyPI, still do this. We can revisit later when deemed appropriate.

Closes

By Submitting this PR I confirm:

• I am familiar with the Contributing Guidelines.
• We require that all contributors "sign-off" on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license.
  • Any contribution which contains commits that are not Signed-Off will not be accepted.
• When the PR is ready for review, new or existing tests cover these changes.
• When the PR is ready for review, the documentation is up to date with these changes.

Summary by CodeRabbit

• Chores
  • Updated litellm dependency version constraints to a specific range across multiple packages.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4d66130a-9b36-4b04-9d8c-fa12f446ff71

📥 Commits

Reviewing files that changed from the base of the PR and between 2a9bf12 and b990c16.

⛔ Files ignored due to path filters (6)

• examples/frameworks/adk_demo/uv.lock is excluded by !**/*.lock
• examples/frameworks/agno_personal_finance/uv.lock is excluded by !**/*.lock
• packages/nvidia_nat_adk/uv.lock is excluded by !**/*.lock
• packages/nvidia_nat_agno/uv.lock is excluded by !**/*.lock
• packages/nvidia_nat_crewai/uv.lock is excluded by !**/*.lock
• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• packages/nvidia_nat_adk/pyproject.toml
• packages/nvidia_nat_agno/pyproject.toml
• packages/nvidia_nat_crewai/pyproject.toml

---

Walkthrough

The litellm dependency version constraint was updated across three NVIDIA NAT package configuration files. The constraint was changed from a compatible-release version specifier to an explicit bounded range, modifying from litellm~=1.74 to litellm>=1.74,<1.82.7 in each package.

Changes

Cohort / File(s)	Summary
Litellm Dependency Constraint Updates packages/nvidia_nat_adk/pyproject.toml, packages/nvidia_nat_agno/pyproject.toml, packages/nvidia_nat_crewai/pyproject.toml	Updated litellm dependency from ~=1.74 to >=1.74,<1.82.7 across all three packages, replacing compatible-release versioning with an explicit upper bound.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ 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 clearly and concisely describes the main change: pinning LiteLLM to a known-good version across multiple packages, matching the PR objectives and summaries.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mnajafian-nv]

LGTM!

[dagardner-nv]

/merge