Menu
Bump pegaflow-llm package version. Use when the user asks to bump version, release a new version, increment version, or update package version.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when configuring, deploying, or troubleshooting pegaflow-server/pegaflow-metaserver. Covers CLI flags, pool sizing, SSD cache, NUMA, metrics, and multi-node setup.
Use when modifying python/src/lib.rs (PyO3 bindings), python/pegaflow/connector/ (vLLM KV connector), python/pegaflow/sglang/ (SGLang radix cache), .pyi type stubs, or building with maturin.
Debug vLLM async KV loading and PegaFlow connector behavior. Use when investigating async KV loads, WAITING_FOR_REMOTE_KVS states, load/save intents, connector metadata flow, prefetch behavior, or preemption interactions in vLLM scheduler/worker code.
| name | version-bump |
| description | Bump pegaflow-llm package version. Use when the user asks to bump version, release a new version, increment version, or update package version. |
Bump the pegaflow-llm Python package version by directly editing python/pyproject.toml.
Important: Create a branch first since pre-commit hooks forbid commits to master.
grep -E "^version" python/pyproject.toml
git checkout -b release/v<new_version>
python/pyproject.toml:Update both version fields:
version = "<new_version>" (under [project])version = "<new_version>" (under [tool.commitizen])Example: 0.0.10 → 0.0.11
git add python/pyproject.toml
git commit -m "chore: bump version to <new_version>"
git push -u origin release/v<version>
gh pr create --title "chore: bump version to <version>" --body "Release v<version>"
User will manually create the GitHub release via the web UI or CLI.