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.
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 🎉
We’ve added markdown support, owner roles, and an improved UI.
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!
We’ve also been busy cooking up some new features that we think will be game-changers for how your team uses Runway. Here’s a preview of what’s coming:
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 for review on App Store Connect or the Play Console, all without leaving Runway.
Are you making use of phased releases? Update your phased release state (iOS) or increment your rollout percentage (Android) through Runway.
We built App Home as a quick overview of the most important releases for your app.
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.
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”.
We recognize that planning for future releases is a key part of a good release process. That’s why we’ve reimagined the ‘Kickoff’ step to surface more of the important details of an upcoming release, and to give your team more flexibility to make changes as needed.
Check out some of the new features we’ve added to the Kickoff step:
Scheduling: Now, you can easily see target kickoff and release dates for a given version. If you set target dates, Runway will send your team a Slack notification before key dates as a reminder.
Edit release settings: You can also modify the details of your release, like release type (major, minor, point), release pilot, and target dates.
Release description: Add some notes or information to help you plan your release.
Create release branch: If your team uses release branches, you can now create the release branch directly from the Kickoff step. Soon, Runway will be able to automatically cut your release branch on the target kickoff date.
If you’re looking for checklist items, they have a new home up on the top right of each step: