Runway Documentation
  • About Runway
  • 🚀Getting started
    • Adding apps
    • Setting up your integrations
      • Branching strategies
      • Builds and branches
      • Pattern strings / tokens
    • Preparing your first release
    • Setting up your team
  • 🎛️Using Runway
    • Navigating Runway
    • Build Distro
      • Quickstart
      • Uploading builds for distribution
      • Build Distro buckets
      • Sharing builds
      • Installing builds
      • Signing and provisioning cheat sheet
    • App overview
    • Releases
      • Release overview
      • Feature flags
      • Kickoff
      • Feature readiness
      • Translations
      • Release candidate
      • Regression testing
      • Beta testing
      • Screenshots
      • Metadata
      • Approvals
      • App submission
      • App store review
      • Release
    • Release schedule
    • Rollout
    • Hotfixes
    • Rollbacks
    • Checklists
    • Build matching
    • App settings
      • General settings
      • Team settings
      • Release pilot rotation
      • Integrations settings
      • Profiles and devices
      • Signing keys
      • Health metrics settings
      • Automations settings
      • Notifications settings
      • Schedule settings
      • Beta testing settings
      • Metadata settings
      • Release defaults
      • Checklists settings
      • Custom strings settings
    • Organization overview
    • Organization settings
      • Team
      • SSO/SAML
    • User settings
    • Over-the-air (OTA) releases
  • ⚙️Integrations
    • Integrations overview
    • Version control
      • Azure Repos
      • Bitbucket
      • GitHub
      • GitLab
    • Project management
      • Asana
      • Azure Boards
      • GitHub Issues
      • Jira
      • Linear
      • Pivotal Tracker
      • Monday.com
      • Shortcut
    • CI/CD
      • App Center Build
      • Azure Pipelines
      • Bitbucket Pipelines
      • Bitrise
      • Buildkite
      • CircleCI
      • Codemagic
      • GitHub Actions
      • GitLab CI
      • Jenkins
      • TravisCI
      • Xcode Cloud
    • Regression testing
      • TestRail
      • Xray
    • Beta testing
      • Google Play testing tracks
      • TestFlight
      • App Center
      • Firebase App Distribution
    • App stores
      • App Store Connect
      • Google Play Console
      • Amazon Appstore
      • Huawei AppGallery
      • Samsung Galaxy Store
    • Notifications
      • Microsoft Teams
      • Slack
    • Stability monitoring
      • BugSnag
      • Datadog
      • Embrace
      • Firebase Crashlytics
      • New Relic
      • Sentry
      • Dynatrace
    • Observability & analytics
      • Amplitude
      • Datadog
      • Google Analytics
      • Mixpanel
      • New Relic
      • Custom observability & analytics
    • Feature flagging
      • Optimizely
      • LaunchDarkly
    • Scheduling
      • Opsgenie
      • PagerDuty
    • Translations
      • Crowdin
      • Lokalise
    • Calendar
      • Google Calendar
  • ⚡Automations
    • Automations overview
    • Types of automations
  • 🔔Notifications
    • Notifications overview
    • Types of notifications
  • 🪝Webhooks
    • Outgoing webhooks
  • 📡REST API
    • Overview
    • Reference Docs
    • Markdown Badge API
    • App configuration files
  • 🛠️Quickstart CI/CD
    • Quickstart CI/CD overview
    • Getting started
  • Support
    • Contact us
Powered by GitBook
On this page
  • Localization directories
  • Fixes settings

Was this helpful?

  1. Using Runway
  2. App settings

General settings

Manage your app's general settings

Version files

The file path(s) corresponding to your app's version files. Runway will bump the version in these files during manual or automated version bumps, and parses these files to determine your app's Version in code for the working branch and the release branch.

Version files are populated by default using platform-specific files where versions are commonly found, but you can always customize your app's version files to any files found in your repository.

The default file types that Runway will detect versions in are as follows:

iOS:

  • .pbxproj

  • .xcconfig

  • .plist

  • .json

  • .yaml

Android:

  • .gradle

  • .json

  • .yaml

React Native / OTA:

  • package.json

The table below describes the format (in regex) Runway is expecting to find the version in depending on the file type.

File type
Regular expression
Description
Example

.pbxproj

MARKETING_VERSION = (\d+\.\d+\.\d+)

Matches the string MARKETING_VERSION = (case sensitive) followed by one or more digits separated by a . character

MARKETING_VERSION = 12.2.2

.xcconfig

MARKETING_VERSION = (\d+\.\d+\.\d+)

Matches the string MARKETING_VERSION = (case sensitive) followed by one or more digits separated by a . character

MARKETING_VERSION = 12.2.2

.plist

CFBundleShortVersionString<\/key>\s*<string>(\d+\.\d+\.\d+)<\/string>

Matches the CFBundleShortVersionString</key> string (case sensitive) followed by zero or more white space characters (spaces, tabs, line breaks), followed by the <string> string, followed by one or more digits separated by a . character, followed by the </string> string

CFBundleShortVersionString</key><string>2.2.2</string>

.yaml

version:\s+?(\d+\.\d+\.\d+)

Matches the version: string, followed by one or more white space characters (spaces, tabs, line breaks), followed by one or more digits separated by a . character

version: 12.2.2

.gradle

versionName.*?(\d+\.\d+\.\d+)|versionString.*?(\d+\.\d+\.\d+)

Matches the versionName string, followed by zero or more of any character (except line breaks), followed by one or more digits separated by a . character OR the string versionString, followed by zero or more of any character (except line breaks), followed by one or more digits separated by a . character

versionName 12.2.2

.json

\"version\":\s+?\"(\d+\.\d+\.\d+)\"

Matches the "version": string (case sensitive), followed by one or more white space characters (spaces, tabs, line breaks), followed by the one or more digits separated by a . character wrapped in quotation marks

"version": "12.2.2"

Default (all other file types)

(\d+\.\d+\.\d+)

Matches one or more digits separated by a . character

12.2.2

Localization directories

Fixes settings

Configure settings for work item Fixes found on the Feature Readiness step.

  • Create fixes for open PRs against the release branch: Runway will automatically create a Fix for any PRs that are opened against the release branch.

  • Fix approvals: If enabled, work items designated as fixes will surface an approval status. Team members with sufficient privileges can approve or reject fix requests. Approvals can be performed on the Feature readiness release step.

Runway will only auto-merge cherry-pick PRs against open against the release branch if the fix has been approved in Runway. The following conditions must be true for this behavior to apply:

  • "Fix approvals" are enabled

  • Add pull request GitHub status check for fix request approvals: Runway will include a status check on any pull requests created for fixes going into the release branch. The status check will only pass when the fix request associated with the PR has been approved.

  • Thread related fix notifications: Notifications relevant to a given Fix will be threaded in Slack.

PreviousApp settingsNextTeam settings

Last updated 1 month ago

Was this helpful?

Specify the directory/paths that contain your app's localization files. Localization directories are relevant for teams using the to track the status of their localizable strings.

The "Pull fixes into the release" and Fix approvals is enabled

The "Merge pull requests created by Runway" is enabled

🎛️
Translations release step
automation
automation