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
  • Build released in App Store / Play Store
  • Phased release and staged rollout status
  • Release summary
  • Automated release tasks
  • Release automations
  • Release checklist

Was this helpful?

  1. Using Runway
  2. Releases

Release

PreviousApp store reviewNextRelease schedule

Last updated 1 year ago

Was this helpful?

The Release step shows you the status of your final app update once it has been published, including phased release status, a release summary, and any final release tasks, such as tagging the completed release.

Build released in App Store / Play Store

This module indicates which build was submitted for review, as well as its matching CI build identifier.

Stability

If you have a stability integration connected, you’ll see a short summary here of top line crash rates (rate of crash-free users and rate of crash-free sessions expressed as a percentage), adoption rate, and a list of most frequently occurring crashes with this release. Crashes that are new in the current version will appear in the "New" tab of the stability section.

Phased release and staged rollout status

If your app's platform supports phased rollouts and the current version was released as a phased rollout, a module showing phased release status is shown, with actions to pause or accelerate rollouts manually available from here.

Release summary

The default release summary includes stats on your release like number of work items completed, number of contributors to the release, the release duration, and more. You can configure the default template from App settings > Custom strings, and you can make changes to the release summary for a specific release from the Release step up until the release has gone live.

Automated release tasks

These tasks can be automatically performed by Runway once your app is released, but can also be performed manually from the "Automated release tasks" module.

  • Release tagging — The status of your final release tag for this version, with direct links to the tagged release and final tag commit in your version control system. If needed, you can select or update the tag commit here.

Release automations

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

Release checklist

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

You can also have your release summary automatically distributed via email if you enable the automation.

Runway can automatically tag your releases at the end of the release cycle via the automation. If supported by your VCS provider, a "Release" is also automatically created in your VCS, which includes a list of all commits and their associated project management tickets that were included in the release.

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

🎛️
Checklist items
Distribute release summary at the end of each release cycle
Tag releases at the end of the release cycle
Release app
Tag releases at the end of the release cycle
Attach build artifacts to VCS release record when tagging
Mark releases as completed in project management tool
Halt unstable phased releases
Backmerge changes from the release branch
Release stable phased releases to 100% of users
Delete version-specific release branches at the end of the release cycle
Update status of issue tracking tickets upon release completion
Distribute release summary at the end of each release cycle
Prepare rollback releases
Customized phased rollouts
Customized Android staged rollouts