Collaborate and build consensus even more easily with assignable signoffs and automatic reminders
Many teams rely on Runway’s regression, approval, and checklist items to structure and track the many tasks and signoffs needed throughout dev and release cycles. Now, you can build an even clearer ownership model around these items by assigning them to individual owners.
You can assign items to any individual on your team, or to multiple team members at once – a great way to build shared ownership across distributed product- or feature-based squads. Separately, if you’ve assigned the Release Pilot role, that will now map to the specific person who’s the active Pilot for the release in question.
Assigning important tasks to folks is one thing – actually getting them to take care of those tasks is another. Runway’s new checklist item reminders help you avoid the usual chasing-down and cat-herding.
As your target submission and release dates approach, Runway will proactively send notifications into Slack reminding the owners of any pending tasks to complete them. If needed, you can also manually ping owners of specific items or trigger reminders for all incomplete items, right from Runway.
Spend even less time in App Store Connect and Play Console, with screenshots and more metadata now handled in Runway
Since the beginning, one of the core aims of Runway has been to keep teams from ever needing to set foot in App Store Connect or Google Play Console.
Recent additions to Runway’s Metadata and Screenshots steps help make that possible in even more situations: you can now update your app’s screenshots, along with keywords on iOS and your app’s short description on Android.
Offload all of your user management for the app stores
We’ve heard from many of you that keeping users up to date in App Store Connect and Google Play Console as team members come and go can be a huge time sink. So, we’re excited to introduce Runway’s new user sync automation. With the automation enabled, we’ll sync your team members from Runway to App Store Connect and Google Play Console as needed: inviting new team members, with the appropriate roles assigned, and removing access when team members leave your org.
(Available on the Runway Pro plan and above)
Keep closer tabs on quality, mobile org performance and maturity
We’re continuing to expand the types of stats and metrics you can keep tabs on with Runway, to help your team better understand how your app’s quality, performance, and process maturity are tracking from release to release.
One new addition on the iOS side is the ability to track how your app’s bundle size changes over time. And for both iOS and Android, see average user rating per release.Â
At the app and org levels, you’ll notice that insights on hotfixes are now surfaced, both total counts and average numbers of hotfixes your team is needing to ship per regular release.Â
More options for beta distribution, with our new App Center Distribute integration
If you’re using App Center to distribute beta or other pre-prod builds to testers, you can now hook that up to the beta testing step in Runway. Easily update release notes, distribute new builds to your preferred testing groups, and keep tabs on the latest available builds side-by-side with the rest of your release process in Runway.
A dedicated monitoring overview for more confident rollouts
It can be tricky, and time-consuming, to bounce between browser tabs and keep track of important markers of release health as you run your rollouts. Runway already pulls in a lot of the important signals, and now we’re giving them a real home! With the new Monitoring section in each release, we’re consolidating stability monitoring, user reviews, phased release status and, soon, product analytics – giving you one place to go to keep tabs on the health of rollouts.
Slack slash commands: an even easier way for your team to chip in
We know that different team members collaborate on releases in different ways, and sometimes folks need to weigh in more efficiently. That’s why we’re introducing Runway slash commands in Slack. Your team can now do things like update the status of regression testing, mark a checklist item as completed, or update an Approvals item, just-in-time and all without leaving Slack. To see a list of available commands, just type `/runway help`. And, if there are other Runway actions you’d like us to add, let us know!
Understand exactly what’s happening, and when, with richer event timelines
With so many moving pieces, it can be hard to keep track of everything that’s happening during release cycles – and even harder to make sense of things after the fact, if you need to retro or audit a release. To help your team understand exactly what is changing during releases, across all your tools and contributors, we’ve revamped event timelines in Runway. At release level, and also within individual steps, you now get a more complete and detailed picture of every single change and status update – plus, key upcoming lifecycle events and deadlines.  Â
New automation: backmerge changes from the release branch
For teams that apply late-arriving fixes to release branches, merging those changes back into your working branch (not to mention any other in-flight release branches) is an annoying manual process that wastes your time week-in, week-out. Now, Runway can automate all backmerges for you!    Â
You can now leverage Runway’s powerful functionality in concert with your team’s own internal tooling with the new Runway REST API. Using the API, you can create and update releases in Runway, update the status of checklist items, and more. To get started, create an API key from your organization’s settings page, then head to our API reference docs to learn more about the types of endpoints available.Â
Missing something your team needs? Let us know! We’ll be expanding the functionality of the API based on feedback.
(Available on the Runway Pro plan and above)
Outgoing webhooks
In the other direction, if you need Runway to call out to your stack when certain changes happen during release cycles, this can now be accomplished using outgoing webhooks. You can hook into events like release kickoff or rollout, release pilot changes, and checklist item status updates (plus many more!) to further customize your release workflow in response to changes happening within Runway and across your tools.
To get started using webhooks, add a new endpoint in the Webhooks section of your organization’s settings. You can choose which event types to subscribe to, as well as the specific apps you’re interested in receiving events for.
To see the full list of event types supported, and to explore the structure of the webhook payloads, check out our webhooks reference docs.
(Available on the Runway Pro plan and above)
New automations
Automatically carry over beta tester notes
We often hear that teams care about putting together beta tester notes for each release, but they waste time having to manually copy-paste the notes every time a new beta build lands.Now, Runway can automatically carry over your “What to Test” or “Release notes” from a previous beta build to the next ones.
If your team is one of the ones that always has to provide review attachments when you submit your iOS updates, you no longer need to waste time manually uploading those each and every release. Save your usual review attachment in Runway just once, and we’ll handle the rest automatically going forward.
‍Improve your release practice with release insights
Get a better understanding of how things are tracking throughout your release cycles and identify any areas that could use extra attention or improvement with release insights. Runway collects a whole range of statistics over the course of each release, and now we’re aggregating and surfacing that relevant data in a number of ways.
Release overview
At the top of the release timeline, you’ll now find the Release overview page. Here, you can see a number of important high-level statistics about your release broken out into different sections. The specific data surfaced depends on whether the release has already been completed or is still in progress, ensuring what you see stays contextually relevant. Some examples include:
The number of items of work that went into the release
The top contributing product teams for the release
The total number of commits in the release
The top code contributors for the release
The top files changed in the release
Timing info: cycle duration, average build times, review times, and more
Many statistics on the page also surface a “Change” value, representing the difference in this stat between the current release and a historical average across previous releases. Looking at changes is a great way to pinpoint areas of your team’s release process that perhaps need special attention or could use improvements.
Organization overview
The Organization overview page zooms out and looks at release stats in aggregate for your apps and your whole organization. Here, you can view statistical averages and associated trends, at the level of granularity that makes the most sense for your organization. This is a great way to keep tabs on the bigger picture, and it provides a new level of visibility both for your immediate team and for other stakeholders.Â
Be sure to keep an eye on these new Release and Organization overviews – we’ll continue to add more insightful stats that can help your team gain a better understanding of how your releases are tracking over time and where improvements could be made. Have a specific statistic you’d like to see surfaced in these views? Don’t be shy – let us know!
Track down bugs more seamlessly with stability issue root-cause associations
Runway will now analyze new stability issues in each release and match them with suspect commits to help you more quickly identify their root cause and speed up triaging!
When Runway detects one or more potentially suspect commits for a new stability issue, you’ll see a special icon next to it in the list of top issues for the release. Clicking on that issue opens a new drawer, with a list of commits that Runway flagged as potential culprits.
Additionally, Runway will highlight any work items in the Feature Readiness step that contain code that has been flagged as suspect. Clicking into the work item’s drawer, you’ll now find a stability issues section which lists any issues that were linked to the work item.
Finally, a new stability issues filter on the Feature Readiness step will let you quickly find all suspect work items that have been linked to one or more specific stability issues.
Teams rely on the Feature Readiness step to understand exactly what is shipping with each release, and to identify inconsistencies and potential blockers before they turn into showstoppers. We’ve now made this even easier and more dependable.
A new look, and even more info
There’s a new tabbed layout, allowing you to easily jump between “pending” and “done” buckets, and item-level data is rearranged for at-a-glance clarity and to accommodate more useful info, like project names and ticket labels.Â
Clicking on an item’s row will open a new details drawer. Navigate here to see the full run-down on a particular item of work, with extra info drawn from across your different tools.
Item-level build info
We’re especially excited to add associated builds to the Feature Readiness step, to help point your entire team in the right direction when they need to check out particular work. Runway will now surface the latest relevant build each item of work can be found in: either your latest or selected Release Candidate build, or else the latest working branch build. (Or, if the item of work hasn’t yet appeared in any build, that’s communicated clearly as well.)
Note that if your working branch build workflow is different than your Release Candidate workflow, you’ll want to hop into your app’s CI/CD integration settings in Runway and set the correct working branch workflow to get fully up and running.
More filters, and sorting
We’ve added even more filters that you can use to hone in on specific subsets of items: you can now filter items by project, ticket owner, code author, and code or ticket status. And, with the addition of various sorting options, you should be able to fine-tune the Feature Readiness view to make it most useful both to you as an individual contributor and on a team level.Â
Top stability issues
Runway now shows top stability issues for every release! These are surfaced both on the app overview screen and on the “Release” step within each release. New issues for a given release are bucketed and highlighted accordingly. (Available for Bugsnag and Sentry integrations to start with; we hope to follow with Firebase Crashlytics soon.)Â
Self-service user management
Although we’re always happy to help out with user management, you can now do more of that yourselves! Runway now supports self-service editing of user roles and removal of users from your organization. For either action, head to your org settings screen and click the gear icon next to a user.
