fix: relax pydantic requirements

[dmitry-tokarev-nv]

Overview:

This PR should fix this conflict:

Because ai-dynamo-runtime==0.7.0+f49d6873e depends on pydantic>=2.10.6,<=2.11.7 and vllm==0.11.1 depends on pydantic>=2.12.0, we can conclude that ai-dynamo-runtime==0.7.0+f49d6873e and
      vllm==0.11.1 are incompatible.

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Chores
  • Updated dependency constraints to support a broader compatibility range.

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

[coderabbitai]

Walkthrough

A single dependency constraint update in the requirements file loosens the pydantic upper version bound from 2.12 to 2.13, with an accompanying comment modification to reflect the rationale for this change.

Changes

Cohort / File(s)	Summary
Dependency Version Update container/deps/requirements.txt	Updated pydantic constraint from >=2.11.4,<2.12 to >=2.11.4,<2.13, widening the upper bound. Accompanying comment updated to explain the dependency rationale related to aiconfigurator and vllm.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file with straightforward version constraint modification
• No logic or functional changes involved
• Comment update is explanatory in nature

Poem

🐰 A version bump, so light and free,
From 2.12 to 2.13,
Dependencies dance with gentle grace,
Pydantic finds its wider space! ✨

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description identifies the core problem (pydantic version conflict between dependencies) but omits critical details: specific file changes, exact version bumps, and rationale are missing or incomplete.	Expand the Details section to specify that container/deps/requirements.txt was modified, explain the version change from <2.12 to <2.13, and clarify why this range resolves the aiconfigurator/vllm compatibility issue.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: relaxing pydantic version constraints from <2.12 to <2.13 to resolve dependency conflicts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 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 0a517dc and 53dbc37.

📒 Files selected for processing (1)

• container/deps/requirements.txt (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: keivenchang
Repo: ai-dynamo/dynamo PR: 4571
File: container/deps/requirements.txt:40-40
Timestamp: 2025-11-26T02:29:06.581Z
Learning: In the ai-dynamo/dynamo repository's version pinning strategy for Python requirements files, "Never use >=" means never use >= alone without an upper bound. Bounded ranges like `>=X,<Y` are acceptable as they prevent untested future versions while accommodating compatibility constraints.

📚 Learning: 2025-11-14T03:26:06.160Z

Learnt from: jasonqinzhou
Repo: ai-dynamo/dynamo PR: 4331
File: tests/profiler/test_profile_sla_aiconfigurator.py:118-121
Timestamp: 2025-11-14T03:26:06.160Z
Learning: The aiconfigurator (aic) only supports sglang version 0.5.1.post1 in its database, so tests should use this specific version rather than the latest available sglang release.

Applied to files:

• container/deps/requirements.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: operator (amd64)
• GitHub Check: vllm (amd64)
• GitHub Check: trtllm (amd64)
• GitHub Check: sglang (arm64)
• GitHub Check: operator (arm64)
• GitHub Check: sglang (amd64)
• GitHub Check: trtllm (arm64)
• GitHub Check: Build and Test - dynamo

🔇 Additional comments (1)

container/deps/requirements.txt (1)

42-42: Verify aiconfigurator and ai-dynamo-runtime compatibility with pydantic 2.12.x before merging.

The constraint change from <2.12 to <2.13 relaxes the upper bound to accommodate vllm's requirement of >=2.12.0. However, the comment states "aiconfigurator 0.4.0 needs ~=2.11.4", which typically means 2.11.x only. If aiconfigurator does not support pydantic 2.12.x, this change will break it. Similarly, the PR objectives mention ai-dynamo-runtime depends on <=2.11.7, but the constraint now permits 2.12.x versions.

Please verify the following before approving:

1. Does aiconfigurator (at commit 5554d2eb8206738c66048bf2d72183e9bcd85759) actually support pydantic 2.12.x and 2.13.x, or does it only work with 2.11.x?
2. Does ai-dynamo-runtime (0.7.0+f49d6873e) support pydantic 2.12.x versions, or is it constrained to <=2.11.7?
3. Has this constraint been tested with all three components (aiconfigurator, ai-dynamo-runtime, vllm) together?

If aiconfigurator or ai-dynamo-runtime cannot support 2.12.x, a more nuanced approach may be needed—such as pinning a newer aiconfigurator version that supports 2.12.x, or finding a pydantic range that satisfies all three dependencies without breakage.

---

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

[nv-anants]

need to bump here as well? - https://github.com/ai-dynamo/dynamo/blob/main/lib/bindings/python/pyproject.toml#L29