Phoenix Release Please

DevOps & Security

phoenix-release-please

Phoenix Release Please is an Agent Skill for devops & security published in the Arize-ai/phoenix repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Bump the next release-please version for a Phoenix Python package (arize-phoenix, arize-phoenix-client, arize-phoenix-evals, arize-phoenix-otel) by opening a PR with a Release-As commit footer. Use this skill when the user asks to "set the release-please version", "force a 2.0.0 release", "release X as Y", "skip a version", or otherwise wants release-please to propose a specific version on its next run instead of the version it would pick from conventional commits.

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/Arize-ai/phoenix/blob/HEAD/.agents/skills/phoenix-release-please/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/phoenix-release-please, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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's version or .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.