Product Updates

Redesigned releases timeline

‍We’re spending time improving how releases are displayed in the timeline. You’ll now see releases separated into “Upcoming”, “Active” and “Completed” buckets, helping call attention to your imminent release. 

Release-type-specific checklist items

‍Create checklist items that only appear for specific release types. When creating or editing a checklist item, select the release types that you’d like the checklist item to apply to. It will only show up on releases of that type.

‍

Takeoff step

Runway now shows you the connection between your selected App Store Connect build, and the corresponding RC build on CI. If the build selected on App Store Connect is older than the most recent CI build, we’ll show a helpful message to call that out. Mostly likely, you’ll want to make sure the most recent CI build is also the build selected on App Store Connect.

‍

Plus a few more little things:

• If you’ve opted into a phased release, we now display the status of your phased release rollout, including what day of the rollout you’re currently on
• If you’ve opted into a scheduled release, we now display your scheduled release date
• Improved messaging on the App Store Connect status of your submitted build
  

And in case you missed it, we launched Slack notifications and automatic tagging over the holidays. For Slack notifications, make sure to connect the Runway Slack app to your workspace from the integrations screen on Runway. To enable automatic tagging, a GitHub repo admin must accept the updated GitHub permissions, and then you should be all set!

Slack notifications

‍This one’s pretty simple. Connect the Runway Slack app and choose a channel, and we’ll send you updates about the progress of your release. Some things Runway will notify you about:

• When all tasks slated for the release have been completed
• When your app has been submitted for review
• When a new Release Candidate is available
• … and more!

Want to try it out? You can find the Slack integration at the bottom of the integrations page. Once you connect the Runway Slack app to your workspace, you’re all set!

Automatic tagging

‍We know remembering to tag your release on GitHub can feel like a chore, but we also know it’s a super important part of the release process. Tagging means you always know exactly which commit was released for which version, so you can always check out the codebase exactly as it was when you released it – for all of your past releases. That’s why we’re excited to bring automatic tagging into Runway. 

Here’s how it works:

• Runway will automatically tag the commit associated with your App Store Connect build as soon as its App Store status reaches “Processing for App Store” 
• Runway will generate a description of your release based on all the commits and associated tickets that were part of your release
• You’ll see automatically created tags and releases under the “Releases” section on your GitHub project
• If for any reason, Runway was unable to tag your release, we created a nice interface within Runway for you to choose a commit to tag (you can find it in the “Ready for takeoff” step on your release)
• You can always edit any of the tags automatically created by Runway

Please note, to enable automatic tagging, we’ll request updated GitHub permissions which can be approved by any repo admin.

Feature Readiness

‍We’ve gotten a lot of great feedback on our feature readiness screen and how it’s helping your teams understand exactly what’s going into your release, so we’ve put extra time into making that step even better.

• Code now shows the relevant branch name
• We’re now pulling in release-relevant code from all branches, not just release branches. Code not found on the release branch will have the status “Not on release branch”
• Visual improvements: we’re now showing more items, and you can now change how many items display in a single page when you have more than 50 items in a release

‍

App Store steps

‍We got some feedback that the App Store steps visually looked disabled or like they couldn’t be used.

• App Store steps were previously gated by all preceding steps being “Ready”. We removed that requirement so you can leverage information from App Store Connect as soon as a build is available.

‍