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 trailer.
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
-
Verify the bump.
jq . .release-please-manifest.json— target must be strictly greater than the current entry. -
Branch off
main. -
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'sversionor.release-please-manifest.json— release-please owns those. -
Commit with the trailer in the body:
git commit -m "$(cat <<'EOF' chore: release <package> <version> <one-line rationale> Release-As: <version> EOF )" -
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.