Add a version
The response carries the number the new version was given. Nothing is live yet:
callers asking for production still receive whatever that channel points at.
The message is optional and worth writing. It is what someone reading the
history months later has to work from.
Put it live
Separating the two steps is deliberate. You can write a version, review it, try
it against a staging channel, and promote only once it is right.
Roll back
A rollback is a promotion at an earlier number:
Because versions are appended and never overwritten, the version you are going
back to is still exactly as it was.
From the terminal
Content can come from a file, which suits prompts long enough to deserve one:
From CI
Publishing on merge keeps the prompts in your repository and the live version in
sync:
This adds a version without promoting one, so a merge never changes what
production serves on its own. Promote deliberately, by hand or in a separate
job.