Release

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.

You can also have your release summary automatically distributed via email if you enable the Distribute release summary at the end of each release cycle automation.

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.

Runway can automatically tag your releases at the end of the release cycle via the Tag releases at the end of the release cycle 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.

Release automations

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

• 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

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