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
    • Release schedule
    • Rollout
    • Hotfixes
    • 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 Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡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
  • Actions from 'Edit release' button
  • Edit release
  • Complete release
  • Skipped release
  • Delete release
  • Release information
  • Feature affiliations
  • Release branch
  • Version in code
  • Previous release tag
  • Release pilot
  • Release description
  • Kickoff actions
  • Bump version
  • Create branch
  • Promote code
  • Kickoff automations
  • Kickoff checklist

Was this helpful?

  1. Using Runway
  2. Releases

Kickoff

PreviousFeature flagsNextFeature readiness

Last updated 16 days ago

Was this helpful?

The Kickoff step serves as an overview for code and branch-related details, as well as pilot and planning information that may be helpful as your release process is getting started.

Actions from 'Edit release' button

Edit release

Modify basic parameters about your release here:

  • Release version (required) - Enter the planned version number of your next release. Runway will determine whether it's a major, minor, or point release based on .

  • Release pilot - Choose a specific team member to act as release pilot for this release. If no selection is made, Runway will automatically assign a release pilot from a rotation of team members who are for this app.

  • Target kickoff date - Specify a target date for when you plan to kick off this release.

    • For release branch teams, Runway considers a release kicked off when a release branch is detected or .

    • For static branch teams, Runway considers a release kicked off when code is detected past the last release tag, or when from your development branch to your release branch.

  • Target submit date - Specify a target date for when you plan to submit this release to the app store for review.

  • Target release date - Specify a target date for when you plan to release this app update to end users.

Complete release

This action will mark the release as completed in Runway.

  • The release will be moved to the 'Completed' section of releases

  • The next up release will then become the active release.

  • This can be used in cases where there was no automated feedback that the release completed naturally (e.g. complete status from app stores, or a completed CI workflow run for OTA apps)

Skipped release

This action will mark the release as skipped.

  • The release will be moved to the 'Completed' section of releases

  • The next up release will then become the active release.

  • Typically, this option is used when a release hasn't actually been published to the app store or otherwise has not been pushed live to users, but the team wants to mantain a record that it existed.

Delete release

This action will remove the record of this release from Runway's list of planned app versions.

Release information

Feature affiliations

Release branch

Shows the status of the branch that your release will be built from.

  • Release branching teams - Runway checks for a matching release branch for this specific version.

      • If Runway's attempt to create the release branch was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.

  • Static branching teams - Runway monitors the branch you release from to detect new commits past your last release tag.

      • If Runway's attempt to promote code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.

Version in code

Runway detects where your version may be determined in your code, and shows you the status of the associated code on your working branches as well as the branch you'll release from.

    • If Runway's attempt to bump your version in code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.

Previous release tag

The name of the tag for the previous release and a link to the code diff in your version control system (e.g. GitHub).

Release pilot

Release description

You can enter notes here about anything your team needs to keep track of for this version release. These notes are internal to Runway and not visible to app store users. Markdown is accepted.

For example, you might call out in the release description that a major feature is being modified and needs extra attention from the team during the release process.

Kickoff actions

You can use the buttons at the bottom of the Kickoff step to perform key actions during your release kickoff.

Bump version

Runway detects where the app version is referenced in your code and bumps it to match the version number of the current planned release.

    • If Runway's attempt to bump your version in code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.

Create branch

(Release branch teams) Runway will create a release branch for this version.

    • If Runway's attempt to create the release branch was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.

Promote code

(Static branch teams) Runway will promote code from your working branch to your main branch.

    • If Runway's attempt to promote code was unsuccessful, you'll be asked to resolve here by clicking through to the associated PR.

Kickoff automations

You can configure the following Kickoff automations by visiting the Automations tab on this step:

Editing automation settings from an individual release will apply those changes to all of your upcoming releases for that app.

Kickoff checklist

You can add checklist items to this step by visiting the Checklist tab.

Checklist items cover any unique parts of your team's release process and live across all your releases. Steps with checklist items won't be marked as complete (green) in Runway until all checklist items have been completed (in addition to the normal criteria that would mark a step as completed).

Here, you'll see a list of labels / fix versions used in your that are associated with ticketed work for this particular release. Runway uses feature affiliations to that are intended to go out with the release but might not be in the actual code yet (and, optionally, can to tickets that have associated code that is already part of the intended release).

You can set up or manage feature affiliations from the page.

If the release branch was created by Runway (via or using the Create branch button at the bottom of the Kickoff step), you'll see a link to the associated PR here.

If code promotion was performed by Runway (via or using the Promote code button at the bottom of the Kickoff step), you'll see a link to the associated PR here.

You can change the details of your branch setup from the page. Runway may not be able to accurately determine the status of your release if this information is incorrect.

Runway can bump the version in code on your behalf by using the button at the bottom of the Kickoff step. Once the version bump is performed, you'll see a link to the associated PR here.

The name of the associated pilot for this release. This can be changed by editing .

Once the version bump is performed, you'll see a link to the associated PR shown along with on the Kickoff step.

Once the release branch is created, you'll see a link to the associated PR shown along with on the Kickoff step.

Once code promotion has been performed, you'll see a link to the associated PR shown along with on the Kickoff step.

🎛️
Checklists
Bump version
release settings
version in code information
release branch information
release branch information
semantic versioning rules
project management tool
eligible to be release pilots
Integrations settings
Integrations settings
track work items
add missing labels / fix versions
automation
automation
Bump version on working branch
Kick off release on target date
Create new App Store Connect versions when the release is ready to be prepared
Prepare next version in Runway when current release is kicked off
Merge pull requests opened by Runway
created by Runway
Runway promotes code