From f7a5dfd5ae1f26600c38ac3933d08ee73381427a Mon Sep 17 00:00:00 2001 From: "LocalAI [bot]" <139863280+localai-bot@users.noreply.github.com> Date: Fri, 3 Jul 2026 00:45:36 +0200 Subject: [PATCH] chore: :arrow_up: Update vllm-metal (darwin) to `v0.3.0.dev20260701212152` (#10646) :arrow_up: Update vllm-project/vllm-metal (darwin) Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mudler <2420543+mudler@users.noreply.github.com> --- backend/python/vllm/install.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend/python/vllm/install.sh b/backend/python/vllm/install.sh index 35f3b3e8a..d2ac62d2d 100755 --- a/backend/python/vllm/install.sh +++ b/backend/python/vllm/install.sh @@ -119,7 +119,7 @@ if [ "$(uname -s)" = "Darwin" ]; then # can rewrite it. Darwin therefore follows vllm-metal and can lag the Linux # vllm pin (requirements-cublas13-after.txt, bumped independently against # vllm/vllm) until vllm-metal supports a newer vLLM. - VLLM_METAL_VERSION="v0.3.0.dev20260701132215" + VLLM_METAL_VERSION="v0.3.0.dev20260701212152" # The coupled vLLM source version is whatever this vllm-metal release builds # against -- it declares it in its own installer as `vllm_v=`. Derive it from