[Bug]: 1.0.0.dev placeholder doesn't work with uv pip install

[mil-ad]

Your current environment

na

Model Input Dumps

No response

🐛 Describe the bug

The recommended way for pip installing latest wheels (i.e. pip install https://vllm-wheels.s3.us-west-2.amazonaws.com/nightly/vllm-1.0.0.dev-cp38-abi3-manylinux1_x86_64.whl) works with vanilla pip but does not work with uv pip. I raised an issue in uv but I don't think this is a uv bug. Would be great to explore more robust options for this.

Before submitting a new issue...

• Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

[cjackal]

I think the installation guide must be updated somehow like

1. first download the wheel from s3 w/ e.g. curl
2. rename the wheel file with the "correct" version inscribed in the wheel METADATA (it requires some unzip yoga, I suppose)
3. (uv) pip install the renamed wheel file

Current (mis)behavior of pip successfully install wrongly-named wheel file is kind of antipattern - not only uv but many repository managers (e.g. sonartype Nexus) that provide pypi mirror support may also check the wheel filename version with wheel metadata version, which would be main blocker to maintain a private mirror for vllm wheels

[dtrifiro]

The problem is that the wheel files should not be renamed, perhaps we need to rethink the approach introduced in #8919