> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onset.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Versioning

> Attach version numbers to releases and flag pre-releases.

If your product has version numbers, showing them on your release notes makes it easy for customers to tell which build a change landed in.

## Enable versioning

<Steps>
  <Step title="Turn on the version field">
    Go to **Settings → Workspace → Releases** and enable **Version**: *"Include a version number in the release notes."*
  </Step>

  <Step title="Set a version per release">
    A **Version number** field appears in the release editor. Enter whatever scheme you use. It's a free-text field, so `2.4.0`, `2026.7`, and `v14` all work.
  </Step>
</Steps>

## Pre-releases

Enable **Pre-release** in the same settings section to get a pre-release toggle on each release. Marking a release as a pre-release labels it publicly, which is useful for betas, release candidates, and early-access rollouts that shouldn't be read as generally available.

<Tip>
  Pair pre-releases with a [label](/guides/labels) like **Beta** so customers can filter them out of the main feed.
</Tip>