$37
Adapt vLLM-Ascend to upstream vLLM main branch evolution — proactively or reactively.
Determine which workflow the user needs, then Read the corresponding document:
Proactive Upgrade — Read proactive-upgrade.md (in the same directory as this SKILL.md)
CI Failure Diagnosis — Read error-analysis.md (in the same directory as this SKILL.md)
If both signals are present (e.g., user says "upstream changed an API and CI is failing"), prefer CI Failure Diagnosis — fixing active breakage takes priority over proactive analysis.
Both workflows share the common knowledge below. After reading the relevant document, also read reference/error-patterns.md for concrete fix examples — do this immediately if the user's message already mentions a specific error type (TypeError, AttributeError, ImportError, etc.), or whenever you encounter such errors during analysis.
Most fixes require vllm_version_is() guards to maintain backward compatibility:
from vllm_ascend.utils import vllm_version_is
if vllm_version_is("0.16.0"): # pinned release version
# Use old API