You’ve always been able to set a target kickoff date and time for a release in Runway. Now, you can have Runway perform your kickoff on the target date you set – Runway will automatically create a release branch, or promote code from your working branch to your static release branch, on the target date and time. You can also configure the automated kickoff to include a version bump as part of the kickoff sequence. More on that below.
We recently added the ability to bump the version in your codebase to the current release version with the click of a button in Runway. Now, you can automate your version bump event to suit your team’s strategy: pre-kickoff (to the current release version), post-kickoff (to the next release version), post-submit (to the next release version), or post-release (to the next release version).
Runway can now automatically submit your build for App Store or Google review on your target submission date.
Runway will only submit your build for review if all the preceding steps on the release are good to go (green).
On iOS platforms, you can now configure Runway to automatically release your app on your target release date if it’s been reviewed and approved by Apple.
Set default App Store and Play Store release notes for every locale you need to support, and Runway can now automatically apply those defaults to new versions. No more copy-pasting every time!
View testers, testing groups, and distribute testing builds using TestFlight, all from within Runway.
Runway can also automatically submit new TestFlight builds for beta review, so you can get new builds in the hands of your external testers as quickly as possible.
Stay tuned for Play Console testing track support on Android!
