What problem does it solve?
Release-please picks the next version from conventional commits, which makes it hard to force a specific version (e.g., a 2.0.0 major bump or skipping a version) for Phoenix Python packages. This Skill lands a commit with a Release-As trailer so release-please proposes exactly the version you want on its next run.
Core Features & Use Cases
- Version Override: Force release-please to propose a specific next version for arize-phoenix, arize-phoenix-client, arize-phoenix-evals, or arize-phoenix-otel.
- Path-Aware Edits: Guides you to make a real file change inside the correct package path, respecting the root package's exclude-paths in release-please-config.json.
- Squash-Merge Safety: Ensures the Release-As trailer lives in a real commit body so it survives GitHub squash-merge settings.
- Use Case: You want to release arize-phoenix-evals as 2.0.0 instead of the minor bump release-please would infer; this Skill walks you through branching, editing, committing with the trailer, and opening the PR.
Quick Start
Ask the assistant to set the release-please version of arize-phoenix-evals to 2.0.0 and open the PR.