Skip to content

chore: bump v0.5.3rc0#10468

Merged
zhyncs merged 1 commit intomainfrom
zhyncs/v053rc0
Sep 15, 2025
Merged

chore: bump v0.5.3rc0#10468
zhyncs merged 1 commit intomainfrom
zhyncs/v053rc0

Conversation

@zhyncs
Copy link
Copy Markdown
Collaborator

@zhyncs zhyncs commented Sep 15, 2025

Motivation

Modifications

Accuracy Tests

Benchmarking and Profiling

Checklist

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @zhyncs, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a routine version bump for the project, updating the core version number to 0.5.3rc0. This change is propagated across various project files, including Python package configurations, build scripts, and user-facing documentation, to ensure all references align with the new release candidate. The primary purpose is to prepare for an upcoming release by standardizing the version across the codebase and informing users of the latest available development branch.

Highlights

  • Version Bump: The project's version has been updated to 0.5.3rc0 across all relevant configuration files, including python/pyproject.toml, python/pyproject_other.toml, and python/sglang/version.py.
  • Documentation Updates: Installation instructions and documentation examples in benchmark/deepseek_v3/README.md, docs/get_started/install.md, docs/platforms/amd_gpu.md, and docs/platforms/ascend_npu.md have been revised to reference the new v0.5.3rc0 release candidate.
  • Build System Adjustments: The Makefile has been updated to include python/pyproject_other.toml in the list of files that should be updated during versioning operations, ensuring consistency across build configurations.
  • Docker Build Examples: Example Docker build commands in docker/Dockerfile.rocm have been modified to use v0.5.3rc0 for the SGL_BRANCH argument.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@zhyncs zhyncs self-assigned this Sep 15, 2025
@zhyncs
Copy link
Copy Markdown
Collaborator Author

zhyncs commented Sep 15, 2025

After v0.5.3rc0, we can use pip install sglang --upgrade on NVIDIA GPU.

@zhyncs
Copy link
Copy Markdown
Collaborator Author

zhyncs commented Sep 15, 2025

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request bumps the project version to v0.5.3rc0. The version update is consistently applied across various files, including project configurations, documentation, and Dockerfiles. The Makefile is also correctly updated to include python/pyproject_other.toml in the list of files for version updates. The changes are straightforward and appear correct for a version bump.

@zhyncs zhyncs merged commit 86a32bb into main Sep 15, 2025
73 of 145 checks passed
@zhyncs zhyncs deleted the zhyncs/v053rc0 branch September 15, 2025 10:55
HanHan009527 pushed a commit to HanHan009527/sglang that referenced this pull request Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants