Skip to content
Wikitura

Pushing Updates Safely

This page is a practical guide for deciding whether to ship changes via OTA (EAS Update) or via a new native build.

Rule of thumb

Section titled “Rule of thumb”

If package.json has changed, assume you need a new native build (bump version + distribute a new build) rather than OTA.

For the end-to-end build + distribution runbook, see Native Builds.

Push staging features safely

Section titled “Push staging features safely”

  1. Native changes Bump version, create and distribute a new build (staging).

  2. JS-only changes Publish an OTA update (staging channel).

Push production features safely

Section titled “Push production features safely”

  1. Native changes Bump version, create and distribute a new build (production).

  2. JS-only changes Publish an OTA update (production channel).

Push production hotfixes safely

Section titled “Push production hotfixes safely”

  1. Default Ship hotfixes via OTA (fastest + lowest friction).

  2. Exception If it’s a serious native bug (or otherwise requires native changes), bump version and ship a new native build (a new binary) instead of OTA.