Freeze a Build snapshot (owner only)
Freeze the current Workspace content into an immutable snapshot (the reference object for debug runs and publishing).
Guards: the workspace exists and its current content is valid (otherwise 422 with issues); the body may carry expected_revision (409 if modified concurrently between save and freeze). An existing ready snapshot with the same content_hash is reused directly (idempotent optimization, no duplicate rows). api kind is ready immediately; code kind returns 202 and submits an image build (a second submission while one is in flight for the same app is 409 — the single build host is serial anyway). Builds stay allowed while deprecated (self-testing is harmless; what is rejected is a new Release).
Authorizations
DataHub API Key
Path Parameters
Body
POST builds request body (optional): optimistic concurrency guard.
Response
Successful Response
POST builds: api-type builds become ready synchronously (200); code-type builds return 202 building (poll GET builds/{id} until ready/failed).