Put your releases on a schedule, and let Runway take it from there. Choose your cadence frequency (weekly, bi-weekly, or monthly), and configure your kickoff, submission, and release settings. Runway will automatically set target dates for upcoming releases as they approach and, with automated kickoff, submission and release enabled, you can finally run a fully automated release train with Runway as your copilot.
To help you keep track of target dates that were automatically set by Runway according to your scheduled cadence, we include a small cadence icon in the schedule module, which you can access from any release step.
If at any point during your release cycle you need to pause upcoming scheduled automations, you can do that easily. Head to the schedule module and hit the “Pause schedule” button. Pausing your schedule means Runway will not perform any more scheduled automations until you resume. Once you resume, upcoming automations will proceed on their target dates as normal.
If your team uses TestRail for QA and regression testing, you can now view test run status and results within Runway. After connecting TestRail, Runway will automatically pull in test runs associated with your release by name and present details within the “Regression testing” step.
Another new and exciting capability – Runway can now pull in and surface Bugsnag stability metrics like session stability, user stability, and adoption percentage. Right now these are displayed on each completed release’s “Release” step, and soon you’ll be able to see all stability metrics in App Home as well. More providers are also coming soon - Sentry is next up!
You’ve always been able to set a target kickoff date and time for a release in Runway. Now, you can have Runway perform your kickoff on the target date you set – Runway will automatically create a release branch, or promote code from your working branch to your static release branch, on the target date and time. You can also configure the automated kickoff to include a version bump as part of the kickoff sequence. More on that below.
We recently added the ability to bump the version in your codebase to the current release version with the click of a button in Runway. Now, you can automate your version bump event to suit your team’s strategy: pre-kickoff (to the current release version), post-kickoff (to the next release version), post-submit (to the next release version), or post-release (to the next release version).
Runway can now automatically submit your build for App Store or Google review on your target submission date.
Runway will only submit your build for review if all the preceding steps on the release are good to go (green).
On iOS platforms, you can now configure Runway to automatically release your app on your target release date if it’s been reviewed and approved by Apple.
Set default App Store and Play Store release notes for every locale you need to support, and Runway can now automatically apply those defaults to new versions. No more copy-pasting every time!
View testers, testing groups, and distribute testing builds using TestFlight, all from within Runway.
Runway can also automatically submit new TestFlight builds for beta review, so you can get new builds in the hands of your external testers as quickly as possible.
Stay tuned for Play Console testing track support on Android!
We know that bumping your version in code is a manual “to-do” for many teams, and it can be an annoying and error-prone task. So, we made it as simple as the click of a button in the Kickoff step. Runway will automatically increment the version in the right files, and open a PR with the changes against your working branch.
Verifying that screenshots are up-to-date previously meant navigating away into App Store Connect or the Play Console before coming back to Runway to approve the step. Now, Runway automatically pulls in your screenshots on both the iOS and Android sides, so you can make sure everything looks good to go right from within Runway.
Artifacts produced during the CI/CD build process, like crash symbols or even binaries, are now available within Runway’s workflow modules.
Additionally, Runway now appends links to build artifacts in select build-related Slack notifications, giving your whole team an easy and quick way to grab RC builds as they become available.
Lastly, Runway will include final build artifacts as part of your GitHub or GitLab release records, ensuring your team can always access historical artifacts over time.
Note that build artifacts are currently supported for GitHub Actions and Bitrise. Support for CircleCI, GitLab CI, and Jenkins will follow soon!
From automatically selecting your latest build in App Store Connect / Play Console, to queuing up your next release version, Runway is now doing even more to streamline your process and take over manual tasks. You can see a complete list of automations enabled for your app at the bottom of App Settings.
Trigger a new workflow run from anywhere the workflow module appears in Runway, without needing to bounce out to your CI/CD provider.
For teams who deploy from a static release branch (e.g. “production”), you can now promote code from your working branch to your release branch with the click of a button. Runway opens the PR for you, and will merge it in automatically when possible.
We’ve improved discoverability and access to checklist items by giving them their own tab on each step.
Set or update the version release settings of your iOS update from the Submission step. You can continue to edit these settings up until your update is approved by Apple.
Update the fraction of users your Android update is rolled out to. You can also pause, resume, or complete a phased rollout for both iOS and Android directly from the Release step.
If your iOS update needs to be manually released, you can now do that directly from the Release step.
Hover over the info icon on any item in the Feature Readiness step to find out exactly why that item was pulled into this release.
We redesigned the Release Candidate step to include more details about the CI workflow which generates your Release Candidate build; like the commit it was run on, and its associated branch.
