Publish a Release (promote a Build, owner only)
Promote an explicit ready Build to an official version; the version number is fixed at this moment: default = patch+1 over the current largest Release (0.1.0 for the first); an explicit version must be three numeric parts and strictly greater than the current largest (use the override to express a major/minor bump).
Guards: the build exists and is ready; the snapshot re-runs the validation pipeline (the spec may have evolved during the Build’s lifetime); when expected_revision is given, the Workspace must not have been modified concurrently. Concurrent publishes are arbitrated by a uniqueness constraint on (owner, app name, version); when auto-versioning collides, the engine recomputes and retries once. The Workspace is kept after publishing (it may already be ahead of the published snapshot; clearing it would lose unsubmitted edits).
Authorizations
DataHub API Key
Path Parameters
Body
Response
Successful Response