From b759135cb1995e62d932013b37e5c85362ef2545 Mon Sep 17 00:00:00 2001 From: tzhouam Date: Thu, 17 Sep 2026 18:12:25 +0800 Subject: [PATCH] adapter(vllm-omni): target releases/v0.30.0 for the next rebase The v0.29.0 campaign merged as vllm-project/vllm-omni#7230, so wheel pick and commit assignment should now track the v0.30.0 release branch. releases/v0.30.0 is cut (f2aad6aa7) but not yet tagged, and currently carries no cherry-picks beyond the main commit it was branched from. This tracks the branch head; the pin moves to the tag commit once v0.30.0 is released, which is also when docker/Dockerfile.ci can move off a commit wheel and back onto a published release image. Co-Authored-By: Claude Opus 5 (1M context) --- adapters/vllm_omni/manifest.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/adapters/vllm_omni/manifest.yaml b/adapters/vllm_omni/manifest.yaml index ce80c83e1..e8318f1b1 100644 --- a/adapters/vllm_omni/manifest.yaml +++ b/adapters/vllm_omni/manifest.yaml @@ -25,9 +25,11 @@ upstream: kind: fork_tracking repo_path: ${VLLM_UPSTREAM_REPO} remote: origin - # v0.29.0 alignment campaign (audited 2026-09-05): wheel pick and - # commit assignment target the release branch, not upstream main - target_branch: releases/v0.29.0 + # v0.30.0 alignment campaign (2026-09-17): wheel pick and commit + # assignment target the release branch, not upstream main. The branch + # is cut but NOT yet tagged, so this tracks the branch head and is + # re-pinned to the tag commit once v0.30.0 is released. + target_branch: releases/v0.30.0 # Repo-specific slice of the SHARED, human-curated knowledge base (the vendored # community docs at the repo-root `knowledge/` = settings.knowledge_dir;