chore: Update sgl version

[jthomson04]

Overview:

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 SGLang dependency to version 0.5.6 across benchmarking specifications, container deployment environments, and project configurations. This maintenance release ensures all project components utilize the latest SGLang version consistently, improving standardization and compatibility across the entire build and deployment infrastructure while maintaining existing functionality.

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

[coderabbitai]

Walkthrough

SGLang dependency version updated from 0.5.4.post3 to 0.5.6 across three configuration files: benchmarks/pyproject.toml, container/deps/requirements.txt, and pyproject.toml. No behavioral, logic, or API changes.

Changes

Cohort / File(s)	Summary
SGLang dependency version bump benchmarks/pyproject.toml, container/deps/requirements.txt, pyproject.toml	Updated SGLang from version 0.5.4.post3 to 0.5.6 across all three dependency configuration files

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify SGLang 0.5.6 is compatible with existing dependencies (no breaking changes from 0.5.4.post3)
• Confirm version bump is intentional and consistent across all three configuration files
• Check for any known issues or changelog entries for SGLang 0.5.6

Poem

🐰 Hop hop, dependencies align,
From post3 to point-six, oh so fine!
SGLang gets a gentle boost today,
Three configs updated—hip hooray! ✨

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is empty template placeholder text with no actual details about the changes, reasons for the update, or file locations.	Fill in the Overview, Details, Where should the reviewer start sections with actual information about why SGLang was updated from 0.5.4.post3 to 0.5.6, and specify the affected files (benchmarks/pyproject.toml, container/deps/requirements.txt, pyproject.toml).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: Update sgl version' clearly describes the main change: updating the SGLang version dependency across multiple configuration files.
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 2f2a13a and 664dd05.

📒 Files selected for processing (3)

• benchmarks/pyproject.toml (1 hunks)
• container/deps/requirements.txt (1 hunks)
• pyproject.toml (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

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.

📚 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:

• pyproject.toml

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

🔇 Additional comments (4)

benchmarks/pyproject.toml (1)

49-50: Verify aiconfigurator compatibility with SGLang 0.5.6.

Line 43 specifies aiconfigurator as a dependency, but the retrieved learning indicates aiconfigurator only supports sglang version 0.5.1.post1 in its database. Updating to 0.5.6 may cause compatibility issues or test failures if aiconfigurator hasn't been updated. Confirm that aiconfigurator 0.4.0 (or the version specified in release/0.4.0) explicitly supports sglang 0.5.6 before merging.

pyproject.toml (1)

62-66: SGLang optional dependency updated successfully.

The version bump from 0.5.4.post3 to 0.5.6 is correctly isolated to the optional-dependencies sglang block. No immediate issues with this file in isolation.

Note: Ensure the broader aiconfigurator compatibility concern flagged in benchmarks/pyproject.toml is addressed, as other parts of the project may combine aiconfigurator and sglang dependencies.

container/deps/requirements.txt (2)

4-12: Verify SGLang 0.5.6 testing against aiconfigurator.

The version pinning strategy documented in lines 4-12 states that "Every installed version should be explicitly tested, not an unknown future release" and explicitly warns against allowing untested future versions. However, this PR updates SGLang to 0.5.6 without clear evidence of:

1. Testing compatibility with aiconfigurator (line 15), which the retrieved learning indicates only supports sglang 0.5.1.post1
2. Test results confirming 0.5.6 doesn't introduce breaking changes

This contradicts the stated version pinning philosophy. Provide confirmation that 0.5.6 has been tested with the container environment, particularly with aiconfigurator integration.

Also applies to: 55-55

---

55-55: Comment update aligns with other files.

The comment on line 55 correctly reflects the version bump to 0.5.6, consistent with changes across benchmarks/pyproject.toml and pyproject.toml.

---

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

[PeaBrane]

nice, looks like the KV events fix made it in (I think)