Notification settings

We’ve put some effort into improving the self-service experience around notifications, so you can fine-tune exactly which messages go where (even to release-specific channels!). Here’s what that entails:

  • You can now enable or disable each type of notification Runway sends on a granular level. And, specific notification types can be directed to any channel of your choosing, overriding your overall, “Primary channel” selection.
Animation showing configuring a Slack notification type to go to a custom specified channel in Runway
  • We know many teams create release-specific channels for each release, and Runway now supports – and helps automate – that! If a channel setting in Runway includes the “{version}” pattern, Runway will resolve that to a channel name for each release, using the appropriate release version. Additionally, Runway can now automatically create those release-specific channels in Slack if they don’t already exist. 
Animation showing entering a release-specific channel pattern in a Slack notification setting in Runway
  • All channel selections, both “Primary channel” and any notification-specific overrides, now support multiple channels each. If you need certain updates surfaced in more than one place, enter multiple channels and Runway will send messages to all.
Animation showing configuring a Slack notification from Runway to be sent to multiple channels

Custom Android staged rollouts

Many of our Android teams rely on Runway to automate their staged rollouts, and a common ask has been for customization of the default 7-day rollout schedule.

Now, you can customize your staged Android rollouts to suit your team’s needs! In “Release defaults” in your app’s settings, just specify the number of days in your rollout and define the rollout percentage for each day, and Runway will do the rest.

Animation showing configuring a custom multi-day staged rollout in Runway