> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/getting-started/preparing-your-first-release.md).

# Preparing your first release

How to get started with your first release in Runway

Once you have gone through the steps in [Setting up Mobile Release Management](/getting-started/setting-up-mobile-release-management.md) and key integrations are 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.

{% hint style="warning" %}
By default, Runway enables [an automation](/automations/types-of-automations.md#create-upcoming-version-in-runway-when-current-release-is-kicked-off) to create upcoming releases in Runway once your current release is kicked off. 
{% endhint %}

## **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 %}

## 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](https://727226624-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MjFmyReUsbJqDjHEAlW%2F-MlSaY_a43pJjhzGiW9A%2F-MlSeZ5UMoo-cw_YUd7f%2Fprepare-new-release.png?alt=media\&token=5d44a2ca-b2b3-4c3e-837d-af245f0eba5d)

{% 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).