Publish a version
Publishes a new version from a package sent as a .tar.gz request body (up to 20 MiB) with automation.yaml at its root. If the package declares risks the person must allow them; pass consent=true only when they have. Identical contents reuse the existing version (200), a version that needs building answers 202, and a ready one answers 201.
Requires the automations:write permission.
Authorizations
An API key from Settings → API keys, sent as Authorization: Bearer jb_live_…
Path Parameters
The automation id.
64Query Parameters
The person has allowed the risks the package declares.
A note for the version history.
300Body
The package as a gzip-compressed tar archive.
The body is of type file.
Response
Identical contents already existed; that version is returned with reused: true.
The version id.
The automation.
Where the version is.
draft, validating, awaiting_consent, building, published, failed, pruned The automation's definition, as read from automation.yaml: meta, manifest, triggers, steps and policies.
A hash of the package contents. Publishing identical contents again reuses the version.
The built image.
Why the build failed.
Who allowed the risks this version declares.
When.
Where it was built.
When the build began.
When the build ended.
When the version was made.
Whether it is the live version.
Whether it can be restored.
Only when publishing: true if identical contents already existed.