phoenix-release-please

Force release-please to propose a specific version via a Release-As commit trailer.

11.3k|1.1k|Updated Nov 9, 2022
One-click install
npx skills add https://github.com/Arize-ai/phoenix --skill phoenix-release-please
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phoenix-release-please
Source: https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-release-please
Command: npx skills add https://github.com/Arize-ai/phoenix --skill phoenix-release-please

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about phoenix-release-please

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I force release-please to release a specific version?

Land a commit containing a Release-As: <version> trailer in its body, along with a real file change inside the target package path. Release-please will then propose that exact version on its next run instead of inferring one from conventional commits.

How do I bump the version of arize-phoenix-evals or other Phoenix packages?

Branch off main, make a small edit inside packages/phoenix-evals, commit with a chore: message and a Release-As trailer, then open a PR. Verify the target version is strictly greater than the entry in .release-please-manifest.json first.

Why does release-please ignore my Release-As commit?

Release-please ignores commits that touch no files in the package's path, or files under the root package's exclude-paths like docs, js, or tests. For arize-phoenix, edit a file under src/phoenix/ so the change counts.

Why is the Release-As trailer lost after squash merging on GitHub?

The Phoenix repo's squash-merge settings build the commit body from commit messages, not the PR description. A Release-As trailer that exists only in the PR body is dropped on squash, so it must live in a real commit's body.

Can I edit pyproject.toml or the manifest to set the version directly?

No. Release-please owns the version field in pyproject.toml and .release-please-manifest.json, and manual edits conflict with its workflow. Use a Release-As commit trailer instead to override the next proposed version.