We know that getting late-arriving fixes into a release post branch cut can be an annoying exercise. Depending how your team does things, you might be delicately cherry picking changes over onto the release branch, wasting time fix by fix, or else you’re relying on cumbersome backmerges post-release (and dealing with the all-too-common mess that arises when said backmerges are inevitably forgotten!).
Runway’s newest automation streamlines the process of getting fixes into a release by automatically cherry picking specific work that your team flags from the working branch into the appropriate release branch. Any PR that contains a designated, customizable pattern in its title is actively monitored by Runway — as soon as it’s merged into the working branch, Runway will cherry pick the relevant commits and open a PR against the specified release branch. If you also have the “merge Runway PRs” automation enabled, the fixes will be auto-merged once required checks pass — there’s nothing more your team needs to do.
Runway automates away lots of manual tasks throughout the release process, and in doing so, it produces many artifacts along the way. Think pull requests, commit messages, GitHub releases, etc. Runway auto-generates relevant messages and copy to go along with each of these, but teams have told us they want more control over this kind of metadata — to do things like add Conventional Commits prefixes or tailor release changelogs to their liking.
Now, you can customize the strings that appear in Runway-generated artifacts. Take Runway’s version bump automation, for example — the PR that Runway creates with the version bump commit can now be configured with:
To allow for dynamic, relevant text, these custom string definitions support a number of special tokens that can pass in info like the release version, release branch name, CI and store build numbers, release pilot info, and more.
Head to the “Custom strings” section on your app’s settings page to check out the full list of custom string options.
We’ve continued to build on Runway’s new feature flagging integration with the evergreen aim of making Runway the single source of truth for all of your tools, throughout the entire dev and release lifecycle. To pull in additional context teams have been asking for, clicking into a specific feature flag opens up a new detail drawer, surfacing properties like target delivery rules and audiences. From here, you can now also toggle the feature flag on and off to quickly update its status without leaving Runway.
And, we’re happy to announce that we now support LaunchDarkly as our newest feature flagging integration, with more providers coming down the pipeline.
We know folks are relying on Runway’s release pilot rotation to share release responsibilities across their team, so we’ve made it easier to manage exactly who’s on duty, and when. In addition to adding and removing team members from the list of pilot-eligible users, you can now order and reorder the list to configure the exact rotation you want to run.