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…
npx skills add https://github.com/openai/symphony --skill releaseRelease
-
Start from fresh
origin/mainin 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.Ztag. -
Update
elixir/mix.exssoversion: "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
maincommit. Verify itsmix.exsversion, 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-releaseuntil 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.