> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/releases/create-a-release.md).

# Create a release

Release creation starts inside the project—not from the workspace My Releases gallery. The project Releases page scopes the eligible annotated data and exposes the queue, data-type, format, distribution, and export-token controls used for that delivery.

### Before you make the change

* Resolve or explicitly exclude rejected, invalid, failed, escalated, or unreviewed work.
* Choose the downstream consumer and schema requirements.
* Name the release owner and validation owner.

![Project Release dialog showing annotated data, queue scope, data types, format, distribution, and token URL option](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2FHLzEBrP9ddsrTUbQ4ovz%2Frelease-create-modal.png?alt=media\&token=70baced4-91a7-4c40-bf7b-417177d75b90)

*Open Project › Releases and choose Release. The dialog shows the eligible annotated item count, selected queue scope, included data types, export format, train/validation/test distribution, and optional export token URL before creation.*

### Understand the product behavior

Releases are created from a project’s Releases page:

1. The user opens the export dialog.
2. The user chooses the source scope: the full project or one/more Batch Queues.
3. The user selects one or more data families inside that scope.
4. Unitlab previews releasable counts, annotation/review progress, format compatibility, and recommended format.
5. The user chooses an export format or per-family Standard Bundle formats.
6. The user selects a license when required.
7. The user enters nonnegative integer train, validation, and test percentages that sum to 100.
8. The user optionally enables stable tokenized item URLs.
9. Unitlab creates the versioned release.

Invalid latest histories are excluded from ordinary releasable counts. Cloud-storage-sourced releases are forced private.

### Create the controlled delivery

{% stepper %}
{% step %}

#### 1. Open the project Releases page

Enter the approved project and choose Releases in project navigation. The workspace My Releases page is the cross-project gallery, not the creation entry point.
{% endstep %}

{% step %}

#### 2. Open Release

Choose Release and reconcile the eligible Annotated data count before configuring delivery.
{% endstep %}

{% step %}

#### 3. Choose queue scope

Use Whole project or select the intended queues so the release contains the approved operational cohort.
{% endstep %}

{% step %}

#### 4. Choose data types

Include only the Image, Video, Audio, Document, Text, Medical, or grouped types required by the consumer.
{% endstep %}

{% step %}

#### 5. Choose the format

Select UUEF or another supported format that preserves every required geometry, property, relation, temporal field, and group context.
{% endstep %}

{% step %}

#### 6. Configure distribution

Set train, validation, and test percentages with the sliders; keep related entities and Data Groups in one split when leakage control requires it.
{% endstep %}

{% step %}

#### 7. Decide token behavior

Enable Include export token URL only when the approved downstream access model requires it; treat generated tokens and URLs as secrets.
{% endstep %}

{% step %}

#### 8. Create and monitor

Choose Create release, retain the release ID, and wait for terminal processing before opening the release detail and downloading output.
{% endstep %}
{% endstepper %}

### Decisions that affect production

| Decision      | Production guidance                                                                     |
| ------------- | --------------------------------------------------------------------------------------- |
| Queue scope   | Whole project is correct only when every eligible item is approved for this handoff.    |
| Content scope | Make data types, inclusions, and exclusions explicit and reviewable.                    |
| Format        | Choose for downstream fidelity, not convenience alone.                                  |
| Splits        | Use a reproducible policy that prevents leakage across related items or groups.         |
| Token URL     | Enable only for an approved access workflow; never publish or log the resulting secret. |
| Sources       | Balance reproducibility, storage, access, and sensitive-data requirements.              |

### Continue the operating flow

* Inspect sample output and counts.
* Download into a controlled validation environment.
* Record downstream acceptance or required correction.