release

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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

Do not tag an uncommitted or unmerged revision. Do not move a published tag without explicit user approval.

Repository: openai/symphony
Path: .codex/skills/release/SKILL.md
Commit: be10a1b

Last updated: 1 day ago
First committed: 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.