Phoenix Release Please
- 10 installs
- 10.9k repo stars
- Updated August 4, 2026
- arize-ai/phoenix
phoenix-release-please is a Claude skill that forces release-please to propose a specific next version for a Phoenix Python package via a Release-As commit trailer.
About
This skill bumps the next release-please version for a Phoenix Python package by opening a PR with a Release-As commit footer. A developer uses it to force a specific version instead of the one release-please would pick from conventional commits. It covers the four managed packages and the squash-merge gotcha where the trailer must live in a commit body to survive.
- Opens a PR with a Release-As commit footer to override the auto-picked version
- Documents the squash-merge gotcha where the trailer must live in a real commit body
- Handles the arize-phoenix root package exclude-paths edge case
Phoenix Release Please by the numbers
- 10 all-time installs (skills.sh)
- Ranked #183 of 248 Release Management skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
phoenix-release-please capabilities & compatibility
- Capabilities
- version bump · release management
- Works with
- github
What phoenix-release-please says it does
Force release-please to propose a specific next version for a managed package by landing a commit with a [`Release-As`][release-as] trailer.
The squash body comes from **commit messages**, not the PR description — so `Release-As` must live in a real commit's body.
npx skills add https://github.com/arize-ai/phoenix --skill phoenix-release-pleaseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10 |
|---|---|
| repo stars | ★ 10.9k |
| Last updated | August 4, 2026 |
| Repository | arize-ai/phoenix ↗ |
What it does
Force release-please to propose a specific next version for a Phoenix Python package by landing a Release-As commit.
Who is it for?
Overriding the version release-please would pick, e.g. forcing a 2.0.0 release or skipping a version
Skip if: Editing package versions directly in pyproject.toml or the release-please manifest
When should I use this skill?
The user wants to set the release-please version, force a specific release, or skip a version
What you get
release-please proposes the exact target version on its next run
- a PR with a Release-As trailer
- a small real edit inside the package path
By the numbers
- 4 managed packages
- 5-step procedure
Files
Phoenix release-please version bump
Force release-please to propose a specific next version for a managed package by landing a commit with a [Release-As][release-as] trailer.
[release-as]: https://github.com/googleapis/release-please#how-do-i-change-the-version-number
Packages
Declared in release-please-config.json; current versions in .release-please-manifest.json.
| Path | Package |
|---|---|
. | arize-phoenix (root has exclude-paths; touch a file outside them, e.g. src/phoenix/) |
packages/phoenix-client | arize-phoenix-client |
packages/phoenix-evals | arize-phoenix-evals |
packages/phoenix-otel | arize-phoenix-otel |
Procedure
1. Verify the bump. jq . .release-please-manifest.json — target must be strictly greater than the current entry. 2. Branch off `main`. 3. Make a small real edit inside the package path (typo fix, comment cleanup). Without a file change in that path, release-please ignores the commit. Don't edit pyproject.toml's version or .release-please-manifest.json — release-please owns those. 4. Commit with the trailer in the body:
git commit -m "$(cat <<'EOF'
chore: release <package> <version>
<one-line rationale>
Release-As: <version>
EOF
)"5. Open the PR with chore: title and the trailer also at the end of the PR body (defensive, in case squash settings change).
Squash-merge gotcha
Repo settings (verify with gh api repos/Arize-ai/phoenix --jq '{squash_merge_commit_title, squash_merge_commit_message}'): COMMIT_OR_PR_TITLE + COMMIT_MESSAGES. The squash body comes from commit messages, not the PR description — so Release-As must live in a real commit's body. A trailer that exists only in the PR description is dropped on squash and release-please never sees it.
Bumping arize-phoenix (root)
The root package's entry in release-please-config.json lists many exclude-paths (.github, docs, js, packages, tests, tutorials, …). A change inside any of those paths is not counted as a server change. Pick a file under src/phoenix/ (or another non-excluded path) for the path-touching edit.
Related skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.11.2k38.5k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.7k37.5k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.9k71.8k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.6k23.3k
Opensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4.3k238k
Community PublishInstantly share running services with public URLs, list projects on a discoverable dashboard, or open-source code to a community GitHub repository.3.9k21FAQ
Why must the Release-As trailer be in a commit body and not the PR description?
The repo squashes using commit messages, not the PR description, so a trailer that exists only in the PR description is dropped on squash and release-please never sees it.
How do you bump the root arize-phoenix package?
The root package excludes many paths, so you must make the path-touching edit under a non-excluded path like src/phoenix/ for the change to count as a server change.