From eef8e2bb94424a03d0b1779992f533b779583ecf Mon Sep 17 00:00:00 2001 From: tzhouam Date: Tue, 8 Sep 2026 23:51:46 +0800 Subject: [PATCH] ci: advance vLLM 0.29 release pin to 98dff2a81d74 Signed-off-by: tzhouam --- docker/Dockerfile.ci | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker/Dockerfile.ci b/docker/Dockerfile.ci index 363e2b9b0..72bd8f5c6 100644 --- a/docker/Dockerfile.ci +++ b/docker/Dockerfile.ci @@ -1,4 +1,4 @@ -# Target vllm version: releases/v0.29.0 @ d2906cc19586, installed on top of +# Target vllm version: releases/v0.29.0 @ 98dff2a81d74, installed on top of # the v0.28.0 base image via the precompiled wheel pinned below. The pin and # base intentionally differ until an official v0.29.0 base image is published. # @@ -57,7 +57,7 @@ RUN uv pip install --system -e ".[dev]" # (e.g. +gaeee7ef93.cu130) which pip/uv refuse to install from a PEP 503 package index. # The cu130 wheel index lives at //cu130/vllm/ but the actual wheel files # are stored at the top level //. -ENV VLLM_PRECOMPILED_WHEEL_COMMIT=d2906cc1958658f296aeee8b248deea684f56add +ENV VLLM_PRECOMPILED_WHEEL_COMMIT=98dff2a81d747d1dba01a47f939f48c3526d4206 # Keep the base image's CUDA toolkit libs on the loader path. This does NOT by # itself guarantee libnvJitLink.so.13 resolves — the .so.13 JIT linker is # handled separately via ldconfig after the cu130 wheels are installed (see the