Menu

Ship a React Native app to devices on every merge to main with GitHub Actions
📰

Ship a React Native app to devices on every merge to main with GitHub Actions

DEV Community: reactnative·Robin·about 10 hours ago
#DiipiYQu
Reading 0:00
15s threshold

Every merge to main can reach your users' phones without a store review, as long as the merge changed only JavaScript. This tutorial builds that pipeline for a React Native app with GitHub Actions and HotCodePush , the over-the-air (OTA) update service for React Native, Expo, Capacitor and Cordova: one workflow file, a staged rollout that starts at 10 percent, signed bundles, and a pull request check that tells you how many devices a merge would reach before you merge it.

The whole setup is about 30 lines of YAML and one CLI command in your project. What you get is a release process where nobody types a version number, nobody picks a channel per native version, and a change that needs a store release is caught at upload instead of on a user's phone.

What you need

A React Native app on version 0.82 or later with the New Architecture, or an Expo app on SDK 55 to 58.

Node.js 22 or later, locally and in CI.

A GitHub repository with Actions enabled.

A HotCodePush account.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.