> For the complete documentation index, see [llms.txt](https://mercure-technologies.gitbook.io/expo-open-ota/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mercure-technologies.gitbook.io/expo-open-ota/getting-started/branches-and-release-channels.md).

# Branches and release channels

## Branches and release channels

Expo Open OTA separates **update storage** from **update delivery**.

An update belongs to a branch. Each installed app listens to one release channel. A channel maps to a branch. This mapping determines which updates the app receives.

```mermaid
flowchart LR
    U["Publish update"] --> B["Branch: main"]
    C["Release channel: production"] --> B
    A["Installed app"] --> C
```

### Branches

A branch groups updates for the same release line. Branch names often reflect purpose or lifecycle.

* `main` contains production-ready updates.
* `staging` contains updates for pre-release validation.
* `feature-checkout` isolates a specific rollout.

Publishing adds an update to a branch. It does not change what installed apps receive.

### Release channels

A release channel is configured in the app's build. Common channels include `production`, `staging`, `preprod`, and `uat`.

A channel points to one branch at a time. Move the channel to promote a tested branch without rebuilding the app.

For example, map `production` to `main`. Publish and validate an update on `staging`. Then map `production` to the validated branch.

### Why the mapping matters

The channel-to-branch mapping decouples publishing from delivery. This supports controlled rollouts and fast recovery.

* Validate updates before production delivery.
* Promote or roll back by changing a channel mapping.
* Prepare targeted experiments, including future A/B testing.

{% hint style="info" %}
Stateless mode reads branches and channel mappings from Expo. Control plane mode manages them directly in Expo Open OTA.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mercure-technologies.gitbook.io/expo-open-ota/getting-started/branches-and-release-channels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.