Runway product updates changelog

Hi [First name], It's been a busy few weeks for the Runway team: many of us have been on the road at mobile conferences around the world, and we had our entire team together in one place for an offsite in Ireland. Of course, we’ve also been hard at work shipping new features and we’re excited to share the latest highlights below. ✨ New in Runway ICYMI: Introducing Triage by Runway We recently launched Triage to help mobile teams ensure nothing slips through the cracks even as product and release velocity accelerate, and to help humans and agents collaborate better to keep app quality high. Triage is a unified inbox that automatically consolidates incoming issues across all kinds of sources: test results, beta feedback, user reviews in the app stores, crash reports, unhealthy metrics, and more. Duplicates are de-duped, related issues and possible root causes are flagged, and best-suited owners are assigned. From there, you can shepherd work as it makes its way into a release using Runway's Fixes flow, which integrates with Triage. Check out the full announcement here, or feel free to reply here to request a live tour! Assign Triage issues to agents As a quick-follow addition to our Triage launch, you're now able to assign a Triage issue to one of your team’s internal agents to investigate and resolve. Runway provides all of the context it gathered on the issue so that the agent is best positioned to handle the fix. And once a resulting PR is opened, the work can be associated with a fix or fix request in Runway to make the end-to-end lifecycle traceable and to ensure any required approvals are gathered along the way. Integrate directly with Expo EAS to manage OTA alongside app store releases As some React Native teams lean into OTA with Expo, we've seen a growing need for the same release visibility and orchestration that Runway already brings to binary releases. With more stakeholders in the loop and more dependencies to manage, predictable, low-risk OTA calls for a real release framework rather than ad hoc CLI commands. Our new native Expo EAS integration allows your team to coordinate and manage OTA releases alongside your app store releases, with a unified overview for tracking status across everything in flight. You can put OTA releases on a recurring cadence, and Runway will auto-select the latest update group and ship it on schedule. Once updates are live, you can manage rollouts from Runway, or automate incremental staged rollouts entirely. And as with the rest of your releases, Runway keeps everyone looped in with notifications on release progress and reminders for anything upcoming or overdue. Support for GitHub stacked PRs and merge queues Runway now recognizes stacked pull requests in GitHub, and we surface visual references to stacks and PR ordering within stacks on Feature Readiness items. Importantly in the fix request context, Runway understands that each PR in a stack ultimately lands on the base branch at the bottom of the stack, so you can create fixes based on stacked PRs and cherry-pick them just like the non-stacked case. When merging PRs (if you’ve enabled the corresponding automation), Runway can now take into account whether your repo enforces a merge queue and will add Runway PRs to the queue instead of trying to merge them directly. These PRs will merge in the order they joined the queue, and only after their checks and approvals pass. Even more control over how and when fixes can be pulled into releases Runway’s fix request flow and approval settings are now even more flexible. If you don’t necessarily want to require approval for every fix, you can apply conditional approval requirements. For example, if your team is okay with ungated cherry-picks early in release cycles, you can require approvals only once you’re within a certain number of days or hours of your target submission date. You can also now name specific user groups or individuals as required approvers. And, authorized ap