chore: Revert "bump sglang version for 0.6.1 dynamo release (#3911)"

[nv-tusharma]

This reverts commit 666e4aa.

This should hopefully resolve the issues encountered in 5623305 and 5623639.

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 framework version from 0.5.4.post1 to 0.5.3.post2 across configurations and documentation.

[coderabbitai]

Walkthrough

SGLang dependency version downgraded from 0.5.4.post1 to 0.5.3.post2 across Docker configurations, project dependencies, and documentation. The version change is consistent across all affected configuration files with no logic or control flow modifications.

Changes

Cohort / File(s)	Change Summary
Container Images container/Dockerfile.sglang, container/Dockerfile.sglang-wideep	Updated SGLang version arguments: ARG SGLANG_COMMIT and ARG SGLANG_IMAGE_TAG downgraded from 0.5.4.post1 to 0.5.3.post2
Documentation docs/backends/sglang/README.md	Installation instructions updated to reference sglang >= 0.5.3.post2 instead of >= 0.5.4.post1
Project Configuration pyproject.toml	Dependency version constraint updated from "sglang[all]==0.5.4.post1" to "sglang[all]==0.5.3.post2"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Simple, homogeneous version pin changes across multiple configuration sources. All modifications are straightforward version string updates with no logic complexity or control flow alterations.

Poem

🐰 A hop, skip, and a version down,
From post1 to post2 we go to town,
SGLang shifts with graceful ease,
Config files, docs—all please!
The rabbit's work brings harmony. ✨

Pre-merge checks

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Description Check	⚠️ Warning	The PR description contains the required template structure with all section headings present (Overview, Details, Where should the reviewer start?, and Related Issues). However, the Overview, Details, and "Where should the reviewer start?" sections are completely unfilled except for the template comment placeholders, providing no actual information about what the revert accomplishes or why it's necessary. The Related Issues section contains only the placeholder text "#xxx" rather than an actual issue reference. While there is a single introductory line stating "This reverts commit 666e4aa," the overall description lacks the substantive content needed to understand the context, impact, and rationale for the revert.	To pass the description check, the author should fill in each section with meaningful content. The Overview should explain why the revert is necessary and what issue or problem it addresses. The Details section should describe the specific version changes being reverted (the SGLang version changes across multiple files). The "Where should the reviewer start?" section should call out the key files (container/Dockerfile.sglang, container/Dockerfile.sglang-wideep, docs/backends/sglang/README.md, and pyproject.toml). Most importantly, the Related Issues section should reference an actual GitHub issue number instead of the placeholder "#xxx".

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "chore: Revert "bump sglang version for 0.6.1 dynamo release (#3911)"" is fully related to the main change in the pull request. The PR reverts the sglang version from 0.5.4.post1 back to 0.5.3.post2 across four files (Dockerfiles, README, and pyproject.toml), and the title accurately and clearly conveys that this is a revert of the previous version bump. The title is specific and concise enough for a teammate to understand the primary change when scanning commit history.

---

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