vllm-ascend-release

Automates the end-to-end release management workflow for vLLM Ascend on GitHub.

2.7k|2.2k|Updated Jan 29, 2025
One-click install
npx skills add https://github.com/vllm-project/vllm-ascend --skill vllm-ascend-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vllm-ascend-release
Source: https://github.com/vllm-project/vllm-ascend/tree/main/.agents/skills/vllm-ascend-release
Command: npx skills add https://github.com/vllm-project/vllm-ascend --skill vllm-ascend-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, python-dotenv, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Managing a vLLM Ascend release involves many manual steps: creating checklist issues, triaging bugs, tracking must-merge PRs, verifying nightly CI, writing release notes, and publishing announcements. This Skill orchestrates that entire process with scripts and templates while keeping human review at critical decision points.

Core Features & Use Cases

  • Release Checklist Automation: Generates release checklist and community feedback issues on GitHub from templates using the gh CLI.
  • Bug and PR Triage: Scans issues and PRs since the last release, flags release-blocking bugs by engagement, labels, and keywords, and updates the checklist.
  • Nightly CI Analysis: Summarizes Nightly-A2/A3 workflow runs, categorizing failures into code bugs versus environment flakes.
  • Release Notes & Announcements: Fetches commits between tags with contributor statistics, drafts categorized release notes, and generates announcements including a WeChat article.
  • Use Case: A release manager starting v0.15.0rc1 runs the skill to create the checklist issue, scan bugs since v0.14.0, verify nightly status, draft release notes, and prepare the release announcement.

Quick Start

Start a new release cycle for vLLM Ascend version v0.15.0rc1 by creating the release checklist and feedback issues, then scan for release-blocking bugs.

Frequently Asked Questions about vllm-ascend-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a vLLM Ascend release on GitHub?

Use this skill to run the nine-phase release workflow: create feedback and checklist issues, triage bugs, track must-merge PRs, analyze nightly CI, draft release notes, update documentation, execute the release, and generate the WeChat announcement. Scripts like generate_checklist.py and scan_release_bugs.py automate each step.

How do I generate release notes from commits between two tags?

Run scripts/fetch_commits.py with --base-tag and --head-tag to fetch all commits between versions along with contributor statistics. Then analyze commits in a CSV, draft notes following the category structure (Highlights, Features, Performance, Dependencies, Breaking Changes), and create a release notes PR.

What permissions does the GitHub CLI need for release management?

The gh CLI must be authenticated with the repo scope for creating issues, PRs, and releases, plus the workflow scope for triggering CI workflows. Verify with gh auth status before starting the release process.

How are release-blocking bugs identified automatically?

The scan_release_bugs.py script flags issues with high engagement (5+ reactions or comments), labels like bug, regression, blocker, or critical, and keywords such as crash, hang, oom, or fail in titles. Flagged issues still require human review before being added to the checklist.

Can the release be executed fully automatically?

No, release execution requires explicit human approval. The skill automates preparation tasks, but merging the release notes PR, creating the GitHub release, and verifying pipelines are manual steps pending release manager review.

What happens if the release process fails midway?

Check the release checklist issue for current state, resume from the last incomplete step, and update the checklist with failure notes. Most scripts are idempotent and can be safely re-run since issue updates use section replacement.