For the complete documentation index, see llms.txt. This page is also available as Markdown.
Releases overview
Understand release content, provenance, formats, splits, and lifecycle.
A release is a deliberate frozen delivery of approved data and annotations. It records what was included, how it was encoded, how it was split, which source files were bundled, and which project context produced it.
Use this area when: approved project work must become a reproducible training, evaluation, analytics, or audit input.
How this area fits into production
Unitlab Releases overview
The release list is the delivery ledger: name, version, project, status, and ownership should make each handoff understandable before opening it.
What this area controls
What a release contains
A release is a versioned annotation snapshot with:
visibility such as Private or Public;
modality;
version number;
creation date;
item counts;
data preview;
annotation preview;
Clone Release;
Overview, Data, and Settings tabs;
item type, data ID, preview, ground truth, and metadata.
A release can contain video, document, and audio items together. Metadata is represented as structured content: video metadata can include frame, video, and audio facts, while document metadata includes PDF and page information.
Start with the right page
Decision
Production guidance
Plan a handoff
Define release scope and acceptance first.
Create delivery
Choose format, splits, and source inclusion.
Inspect the result
Review Overview, Data, and Settings.
Move downstream
Download and validate in the target consumer.
Reproduce later
Retain versioned provenance and stable identifiers.
Operating boundary
A dataset version freezes source membership; a release freezes delivered project output.
Release creation is asynchronous until processing reaches a terminal state.
The release is not accepted until the downstream consumer validates it.
A production-ready handoff
The release has a named owner, explicit scope, source and schema provenance, format and split contract, processing result, downstream acceptance, and retained stable ID.
