Agent Skills › openai/symphony › release

release

GitHub

指导如何发布 Symphony 版本，包括更新版本号、提交代码、创建 Git 标签及验证 Burrito 自动化发布流程。

.codex/skills/release/SKILL.md openai/symphony

Trigger Scenarios

用户要求发布新版本用户要求打标签或重新打标签

Install

npx skills add openai/symphony --skill release -g -y

More Options

Non-standard path

npx skills add https://github.com/openai/symphony/tree/main/.codex/skills/release -g -y

Use without installing

npx skills use openai/symphony@release

指定 Agent (Claude Code)

npx skills add openai/symphony --skill release -a claude-code -g -y

安装 repo 全部 skill

npx skills add openai/symphony --all -g -y

预览 repo 内 skill

npx skills add openai/symphony --list

SKILL.md

Frontmatter

{
    "name": "release",
    "description": "Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony."
}

Release

Start from fresh origin/main in a clean worktree. Never disturb unrelated local changes.
Pick the requested version. If none is given, use the next patch after the latest vX.Y.Z tag.
Update elixir/mix.exs so version: "X.Y.Z" matches the intended tag. Search the old version and change other files only when they are true release-version sources, not examples.
Run make -C elixir all, then commit, push, create a PR, and land it.
Fetch the merged main commit. Verify its mix.exs version, then create an annotated tag on that exact commit:
```
git tag -a vX.Y.Z <merged-commit> -m "Symphony vX.Y.Z"
git push origin vX.Y.Z
```
Watch burrito-release until it finishes. Verify the build, smoke, and release jobs pass and that the GitHub release has all expected assets.