Automations are various actions that Runway can take on your behalf during the release process. From big actions like submitting your update to the app stores, to more routine manual tasks like bumping version in code or adding your release notes, our continuing goal is to empower teams to think less about the busywork of preparing releases.
Additionally, since Runway sits between your project management, version control, CI, app stores, Slack and other parts of your toolchain, it’s able to perform unattended tasks where an action needs to happen in a particular tool once the status of another tool changes.
When you have automations turned on, you’ll see the lightning symbol showing up in various locations in the Runway app. This might be a reminder that it’s ready to take actions on your behalf (as in the Release timeline, or in the Schedule drawer), or it’s pointing you to a way to check on the status of your pending or completed automations (as in the Automations tab found on many steps).
If your team has ideas for a routine part of your process that could be automated away (or something new that would save you time), please get in touch!
Runway will select the latest available build for release in App Store Connect. Note that there may be a processing delay of a few minutes.
Runway will select the latest available APK/AAB in the production track in the Play Console.
Runway will create a new version of your app in App Store Connect once the next release is being prepared in Runway.
Runway will create a draft production release in the Play Console once the next release is being prepared in Runway.
Runway will download all artifacts generated from your CI build workflow, and provide direct download links to them from the Runway interface. Additionally, Runway will include artifact information in Slack build success notifications, including a link to find those downloads in Runway.
When tagging your production release commit, Runway will attach all artifacts generated from your active production build workflow as assets on your release record.
Runway will apply your default 'What's New' text (as defined in App Settings) to new versions created in App Store Connect. You can continue to modify the text before you submit your update for review.
Runway will apply your default release notes (as defined in App Settings) to new versions created in the Play Console. You can continue to modify the text before you submit your update for review.
Runway will create a new Runway release record for your next version when your current release is kicked off. This will assign a release pilot and provide a selectable upcoming release via the versions timeline in the App Overview screen.
Runway will tag your production release commit at the end of each release cycle, and generate a summary of all work going out with the release.
Runway may create pull requests to fulfill various tasks on demand (for example, bumping your version in code on a development branch). If this automation is enabled, Runway will attempt to merge these PRs without manual approval.
Runway will add appropriate labels and/or fix versions when they are missing from tickets that are associated with the release. These label and fix version patterns are defined in App Settings.
Static branching teams
Runway will promote code from your working branch to your release branch on the scheduled date.
Release branching teams
Runway will create a release branch off of your working branch for the next release on the scheduled date.
Runway will submit your selected build for review on the scheduled date if all previous steps are ready (green).
Runway will release your app update (or start your phased release, if applicable) on the scheduled date if all previous steps are ready (green).
Runway will roll out your release (or start your staged rollout, if applicable) on the scheduled date if all previous steps are ready (green).
Runway will apply your default Export Compliance Information answers (as defined in App Settings) to new builds as they are uploaded to App Store Connect.
Runway will submit any new builds uploaded to TestFlight for beta review as soon as they finish processing.
Runway will promote any newly uploaded APKs/AABs to your testing track and start the rollout.
Runway will assign any new builds uploaded to TestFlight to your default beta groups for testing. External testers will have access once the build has been reviewed.
Runway will bump the version in code on your working branch as defined in App Settings.
Runway will release your update to all users early if the session stability for the update stays within your defined delta relative to your average session stability, and your adoption threshold has been reached.
Runway will pause your phased release / staged rollout if the session stability for the update decreases by a specified percentage relative to your average.