# Preparing your first release

Once you have key integrations set up, preparing a new release in Runway is straightforward. There are a few ways that new releases are added to your app's [release timeline](/using-runway/app-home.md#release-list), described below.

## **New code detected on a static release branch, or a new release branch is detected**

### Version-specific release branch workflow

When Runway detects a new release branch matching your release branch pattern, it will create a new release record with a version number matching the version defined in your release branch on your VCS.

### Static release branch workflow

If your team has a static release branch or a single, trunk-style branch, a new release record will be created by Runway automatically as soon as new commits are detected past your previous release's tag.

{% hint style="info" %}
When creating new releases as a result of new code being detected on the release branch, Runway will, by default, assume the new release has a version equal to a minor version increment from your previous release.

For example, if your previous release was `1.1.0`, and Runway detects new code on your release branch, it will automatically create a new release with the version `1.2.0`.
{% endhint %}

### Versioning config 

Version strings are an important identifier in Runway, allowing us to match up release data across different contexts and integrated tools.

#### Custom versioning configs

Not all teams follow standard semantic versioning, so we offer the ability to set custom versioning configurations that allow Runway to interpret different version string formats and still map them to the correct release. You can set these mappings for different contexts if needed — for example, you could set one config for version strings as they appear in your app’s bundle and in the app stores, and a different one for version strings that appear to users in Runway.

Below are common examples of custom versioning configs. If you’re not sure how Runway might support your team’s versioning convention, get in touch!

* Concise: `3.15`
* Version with build number for patch digit: `3.15.1234` (where `1234` is the store build number that was released)

{% hint style="warning" %}
Currently, custom versioning configs need to be set by the Runway team on our backend. 
{% endhint %}

## Preparing a release manually

You can always choose to manually prepare a release in Runway using the "Prepare release" button on the releases timeline. You will be prompted to enter a version, choose a release pilot, and optionally set target dates for kickoff, submission, and release (depending on your platform).

![Prepare new release modal](/files/-MlSeZ5UMoo-cw_YUd7f)

{% hint style="info" %}
You can always edit a release's details, or delete the release record entirely if needed. Actions for editing and deleting a release can be found on the **Overview** page or the **Kickoff** step's **Summary** tab.
{% endhint %}

### Prepare next release version automation

One of Runway's handy [automations](/automations/overview.md) will automatically create the next-up release in your app's release timeline as soon as your current release is kicked off.

By default, Runway will follow a minor-increment pattern for newly created releases, but you can change this by updating the `Version defaults setting` in [App settings > General > Version defaults](/using-runway/app-settings.md).


---

# Agent Instructions: 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:

```
GET https://docs.runway.team/getting-started/preparing-your-first-release.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.