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.Â
â
â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.
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 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:
Our long-awaited launch of support for Android is finally here, bringing together release coordination across platforms. Hereâs what that means:
â
Send us a note via Slack or email to schedule a time to get your team set up.
âWeâve heard time and time again that keeping release notes in a spreadsheet and copying and pasting them into App Store Connect or Google Play is a headache. Weâve built a real home for release notes in Runway, where your PM or copywriter can come to add release notes and upload them to the relevant app store, for all localizations.
Oh and of course, it works for updating Release Notes on the Play Console as well!
We also added a helpful âFeature listâ button on the Metadata screen, which pulls up all the tickets that are part of the release. We think it could come in handy as inspiration when drafting release notes.