Publish versions
Change a live endpoint through a new version that waits the configured delay before it takes over.
Publish a version
- ScreenMy endpoints
- ActionPublish
- ResultPending
Publish a new versionPending, goes live after the delay
Example dataA version carries model, fallbacks, prompt, files, parameters, markup and a note. Files can be kept, dropped or added: upload a new file on the endpoint, then publish a version that lists it after a passing test.
Test changed behaviour first
- ScreenChanged model or prompt
- ActionVersion test
- ResultPublish allowed
Send a test callTest passed on the platform budget
Example dataChanging model, prompt, files or parameters needs a passing version test first (409 test_missing otherwise), paid from a the test budget daily budget per endpoint. A markup-only change needs no test.
Live after the configured delay
- ScreenPending
- ActionDelay passes
- ResultLive
Cancel the pending versionThe live version stays as it is
Example dataHolders and callers see the pending version and its hashes before it activates. One pending version at a time.
Cancel before it activates
- ScreenPending version
- ActionCancel
- ResultLive version stays
Cancel the pending versionThe live version stays as it is
Example dataCanceling keeps the current live version authoritative.