expo-eas-updatelisted

Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.
fatihkan/badi · ★ 5 · AI & Automation · score 76

Install: claude install-skill fatihkan/badi

# expo-eas-update OTA (over-the-air) update publishing discipline with EAS Update. Channel/branch model, runtime-version strategy, rollback, and embedded vs OTA payload decisions. Build profiles live in `expo-eas-build`. ## What It Does - Publishing JS/asset payloads with `eas update` - Channel ↔ branch mapping management - Runtime-version discipline (`appVersion` / `sdkVersion` / `fingerprint` / custom) - Branch management (preview, staging, production, feature/*) - Rollback and cohort/rollout-percent strategy - Embedded update vs OTA payload selection ## Setup ```bash npx expo install expo-updates eas update:configure ``` `app.json`: ```json { "expo": { "runtimeVersion": { "policy": "appVersion" }, "updates": { "url": "https://u.expo.dev/<project-id>", "fallbackToCacheTimeout": 0, "checkAutomatically": "ON_LOAD", "enabled": true } } } ``` ## Channel ↔ Branch Model | Build channel | Branch | Purpose | |---------------|--------|---------| | development | development | Dev client OTA | | preview | preview | QA test | | production | production | Production | A single branch can be bound to different channels (`eas channel:edit production --branch hotfix-1`). ## Runtime Version Policies | Policy | How it's derived | Usage | |--------|------------------|-------| | `appVersion` | `expo.version` | Native change = new build + new runtime | | `sdkVersion` | Expo SDK | SDK upgrade = new runtime (no longer recommended) | | `nativeVersi