EAS Update Rollout

OTA push for JS, assets, styles without store re-submission. Native code can NOT be OTA'd.

External action gate

Preparing an update is safe; publishing one changes a live product. Before any eas update, eas update:edit, or rollback command, confirm the EAS account, project, channel, runtime version, rollout percentage, monitoring owner, and rollback update group with the owner. Never infer production approval from a request to draft a release plan.

What can / cannot OTA

OTA OK: screens, business logic, copy, styles, assets, react-native libs with no native code, dependency updates within same major.

Requires new binary: new native module, native dep upgrade, Expo SDK bump, app.json key affecting native (permissions, plugins, entitlements, bundle ID, Info.plist), new platform target.