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
  • Preparing hotfix releases
  • Hotfixes and automations

Was this helpful?

  1. Using Runway

Hotfixes

PreviousRolloutNextRollbacks

Last updated 1 month ago

Was this helpful?

Hotfix releases in Runway are special releases that are created off the previous release tag rather than off your team's main working branch. In Runway, the hotfix release process is designed to be as streamlined as possible, and in some cases have special behavior to be aware of.

Preparing hotfix releases

You can create a hotfix release in the Runway app by clicking Prepare release > Hotfix.

By default, roll-forward hotfixes will branch off your live release's tag. You can choose whether you'd like Runway to immediately create a hotfix release branch and bump the version. If you leave these two options unchecked, you will still be able to manually create the release branch and bump the version from the Kickoff step, but doing it as part of the prepare hotfix flow helps streamline the process.

If your team uses a special release branch pattern for hotfix releases (e.g. hotfix-{version}), you can configure that in Integrations > Release branch patterns.

Pulling in (cherry-picking) fixes

You can also optionally select one or more commits from the working branch to pull in as fixes directly. Runway will attempt to cherry-pick the selected commits into the hotfix branch immediately.

Conflicts can sometimes prevent Runway from cherry-picking in selected commits. When that happens, Runway will proceed with creating the hotfix release branch and bumping the version if needed, but will notify of the cherry-pick failure.

Hotfixes and automations

To streamline the hotfix process, Runway will by default skip performing certain automations for hotfix releases. Automations that will be skipped for hotfixes are show with an Inactive status in the Automations tab for the relevant step. A complete list of automations that are skipped by default for hotfixes is outlined below:

You can then choose to create a roll-forward hotfix release by branching off your previous release's tag, or preparing a rollback release. For more information on how to set up, create, and ship rollbacks, visit the documentation.

(Google platforms only)

🎛️
Rollbacks
Add latest build to the production track release
Kick off release
Bump version
Trigger workflow post-kickoff
Submit for review
Release app