[CI/Build] adopt uv

[kemingy]

FIX #184

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

---

• Make sure the code changes pass the pre-commit checks.
• Sign-off your commit by using -s when doing git commit
• Try to classify PRs for easy understanding of the type of changes, such as [Bugfix], [Feat], and [CI].

Detailed Checklist (Click to Expand)

Thank you for your contribution to production-stack! Before submitting the pull request, please ensure the PR meets the following criteria. This helps us maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Please try to classify PRs for easy understanding of the type of changes. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

• [Bugfix] for bug fixes.
• [CI/Build] for build or continuous integration improvements.
• [Doc] for documentation fixes and improvements.
• [Feat] for new features in the cluster (e.g., autoscaling, disaggregated prefill, etc.).
• [Router] for changes to the vllm_router (e.g., routing algorithm, router observability, etc.).
• [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

• Pass all linter checks. Please use pre-commit to format your code. See README.md for installation.
• The code need to be well-documented to ensure future contributors can easily understand the code.
• Please include sufficient tests to ensure the change is stay correct and robust. This includes both unit tests and integration tests.

DCO and Signed-off-by

When contributing changes to this project, you must agree to the DCO. Commits must include a Signed-off-by: header which certifies agreement with the terms of the DCO.

Using -s with git commit will automatically add this header.

What to Expect for the Reviews

We aim to address all PRs in a timely manner. If no one reviews your PR within 5 days, please @-mention one of YuhanLiu11
, Shaoting-Feng or ApostaC.

[kemingy]

Not sure why the setup.py requires 3.12 but some CI test pin 3.10.13.

BTW, copying the .git in the Dockerfile will usually disable all the following cache layers.

[YuhanLiu11]

@kemingy Thanks for the contribution! We will be looking at this soon!

cc @Shaoting-Feng

[Shaoting-Feng]

Thanks for your contribution! Could you help resolve the conflicts? Over the weekend, we added three packages for the router. Could you also include them in the pyproject.toml file?

[kemingy]

Thanks for your contribution! Could you help resolve the conflicts? Over the weekend, we added three packages for the router. Could you also include them in the pyproject.toml file?

Rebased. PTAL.

[Shaoting-Feng]

Thanks for your fix. Could you help make the optioinal dependencies work consistently with the docker build phase? For example, the INSTALL_SENTENCE_TRANSFORMERS argument in the functionality test workflow.

[kemingy]

Thanks for your fix. Could you help make the optioinal dependencies work consistently with the docker build phase? For example, the INSTALL_SENTENCE_TRANSFORMERS argument in the functionality test workflow.

Fixed.