Pattern: Assets to a release

Upload durable assets, publish a dataset version, attach it, wait for processing, and create a release.

Outcome: Upload durable assets, publish a dataset version, attach it, wait for processing, and create a release.

from unitlab import UnitlabClient

client = UnitlabClient()
project = client.projects.create("Quality review")
uploaded = client.assets.upload("./data", folder="Raw data", tags=["incoming"])
uploaded.raise_on_failure()

dataset = client.datasets.create("Review set", folder_ids=[uploaded.folder_id])
version = dataset.publish_version("Initial snapshot")
attach = client.attach_dataset(project, dataset, version=version.version_number)

if attach.batch_queue_id:
    project.batch_queue(attach.batch_queue_id).wait(timeout=1800)

release = client.releases.create(project, export_type="UUEF")
print(release.id, release.version)

Insert annotation and review between attachment and release. The example demonstrates resource boundaries; it does not bypass workflow acceptance.

Operating contract

Concern	Required behavior
Execution surface	Pinned unitlab==3.0.0 application environment on Python 3.10+.
Identity	Least-privilege API key supplied through approved configuration.
Target resolution	Stable resource IDs and an explicitly bounded target set.
Success evidence	Typed return fields, server-side state, and downstream acceptance of the result.

Failure and recovery boundary

Condition	Response
Authentication or authorization fails	Stop, correct the service identity or access model, rotate exposed credentials, and rerun a read-only check.
Validation or entitlement rejects the operation	Correct the input or entitlement; do not retry an unchanged request.
A request times out	Inspect remote state before repeating a mutation because the server may have accepted it.
Asynchronous processing exceeds its deadline	Preserve the Batch Queue or release ID, continue bounded monitoring, and inspect item-level failures.
Only part of a batch succeeds	Keep successful identifiers, isolate failed rows, and retry only the corrected subset.

Pin and test the production SDK version. Use stable IDs, keep secrets out of logs and command history, and record the correlation ID, target IDs, counts, final state, and redacted error details for material state changes.

---

Related Unitlab capability guides: multimodal data curation