Product Updates

More automation

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

Run workflows

‍Trigger a new workflow run from anywhere the workflow module appears in Runway, without needing to bounce out to your CI/CD provider.

Promote code to your release branch

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

A new home for checklist items

‍We’ve improved discoverability and access to checklist items by giving them their own tab on each step. 

Edit your App Store release settings

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

Control your phased rollouts

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

Release your approved iOS update through Runway

‍If your iOS update needs to be manually released, you can now do that directly from the Release step.

Feature Readiness item info tooltips

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

Improved Release Candidate workflow module

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

Automatic Jira fix versions and labels

Any time we detect code on your release branch, and that code is linked to a Jira ticket, we check that the ticket has the correct fix version and/or label applied to it.

For example, here’s a PR (#28) that was merged into the release branch (release-0.0.2). It references ticket RA-11, but that ticket is missing a fix version and label for 0.0.2.

‍

‍

Runway will now automatically add the correct fix versions and/or labels to tickets, as specified in your app settings. In the example above, we specified both a label and fix version in Runway settings, so both were automatically added  🎉

‍

Improved checklist items

‍We’ve added markdown support, owner roles, and an improved UI. 

‍

Select build/APK on Runway

‍Choose which build to submit from a list of most recent builds, and update your selection in App Store Connect/Google Play directly on Runway.

Submit your app through Runway

‍Submit your app for review on App Store Connect or the Play Console, all without leaving Runway.

Update your Phased Release or Staged Rollout percent

‍Are you making use of phased releases? Update your phased release state (iOS) or increment your rollout percentage (Android) through Runway.

The last few weeks have been exciting ones for the Runway team – we participated in Y Combinator’s Demo Day and closed our seed round of funding 🎉 You all played a part in us reaching this milestone, so a heartfelt “thank you” from our team to yours!

App Home

‍We built App Home as a quick overview of the most important releases for your app. 

• Live release: At the top, you’ll see a summary of the release that’s currently live on the app store. Some details here include the date it was released, how long your release cycle took, and your current App Store rating.

• Next release: Here, you’ll see how close you are to being feature complete, a timeline of important events that have happened so far for that release, and key dates.

• Upcoming release: These are releases that are planned for the future, and will show the release description, the pilot slated for the release and key dates like the target kickoff.

Working branch Feature Readiness‍

We’ve heard that sometimes it’s useful to track progress towards a release before it’s actually been kicked off. So, we’ve added the ability to switch your base branch in feature readiness, so you can view progress towards the release relative to your main development branch. Just be sure to set a working branch in your App Settings if you haven’t already.

Ignore button on Feature Readiness

‍Sometimes you don’t want a piece of work to be counted towards the release, but still want to get to feature complete on Runway. We added the option to ignore an item of work so it won’t be considered in determining Feature Readiness. You can always bring back that item by clicking “Include”.