[main to main] upgrade main 0210

[wxsIcey]

What this PR does / why we need it?

upgrade vllm commit to 9562912cead1f11e8540fb91306c5cbda66f0007

Does this PR introduce any user-facing change?

N/A

How was this patch tested?

all tests passed

• vLLM version: v0.15.0
• vLLM main: vllm-project/vllm@1339784

[gemini-code-assist]

Summary of Changes

Hello @wxsIcey, I'm Gemini Code Assist¹! 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 updates the versioning policy documentation to align the main branch of vLLM Ascend with a more recent vLLM commit. This ensures that the documented compatibility information remains current and accurate for users and developers.

Highlights

• Documentation Update: The vLLM commit hash referenced in the versioning policy documentation for the main branch has been updated to reflect a newer version.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• docs/source/community/versioning_policy.md
  • Updated the vLLM commit hash for the main branch compatibility table.

Ignored Files

• Ignored by pattern: .github/workflows/** (6)
  • .github/workflows/_e2e_test.yaml
  • .github/workflows/bot_pr_create.yaml
  • .github/workflows/dockerfiles/Dockerfile.lint
  • .github/workflows/pr_test_full.yaml
  • .github/workflows/pr_test_light.yaml
  • .github/workflows/schedule_codecov_refresh.yaml

Activity

• No specific activity (comments, reviews, etc.) has been recorded for this pull request yet.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. ↩

[github-actions]

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

• A PR should do only one thing, smaller PRs enable faster reviews.
• Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
• Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

[gemini-code-assist]

Code Review

This pull request updates the vLLM commit hash for the main branch in the versioning policy documentation. The current pull request title and description do not follow the repository's style guide. To align with the contribution guidelines, I suggest updating them as follows:

Suggested PR Title:

[Doc][Misc] Update vLLM commit hash for main branch

Suggested PR Summary:

### What this PR does / why we need it?

This PR updates the compatible vLLM commit hash for the `main` branch in the versioning policy documentation. This ensures the documentation reflects the latest supported vLLM commit.

### Does this PR introduce _any_ user-facing change?

No, this is a documentation-only update.

### How was this patch tested?

N/A (documentation update).

[wxsIcey]

https://github.com/vllm-project/vllm-ascend/actions/runs/21889705770/job/63192793626?pr=6673 all tests have passed