Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Workflows
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
      • Creating rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Android Vitals
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
      • Google Calendar (OAuth)
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • New code detected on a static release branch, or a new release branch is detected
  • New feature affiliation detected
  • Preparing a release manually
  • Prepare next release version automation

Was this helpful?

  1. Getting started

Preparing your first release

How to get started with your first release in Runway

PreviousPattern strings / tokensNextSetting up your team

Last updated 5 months ago

Was this helpful?

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 , 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.

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.

New feature affiliation detected

During the setup process, you define a that allows Runway to map tickets in your project management system to a particular release. A new release record will be created in Runway if it detects a ticket with a matching feature affiliation pattern, but no matching release record yet exists for that version.

For example, if Runway detects a ticket in Jira with an ios-1.1.0 fix version, and in Runway, you've defined the feature affiliation pattern ios-{version}, Runway will associate that ticket with your 1.1.0 release. If a 1.1.0 release record does not yet exist in Runway, a new record will be created.

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

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 Kickoff step's Summary tab.

Prepare next release version automation

One of Runway's handy 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 .

🚀
automations
App settings > General > Version defaults
feature affiliation pattern
release timeline
Prepare new release modal