chore(mobile): publish OTA updates to production on every merge to main

Merged
SA
1mo ago
+28-5

Why

TestFlight and App Store builds share the production channel. Until now it only received updates when someone dispatched update-production.yml and approved it. So installed builds fell behind main, while the API and host-service ship with every merge. A build on old JS then hits server changes without the client side of those changes. That is a source of bugs during migrations.

Change

  • deploy.yml adds publish_production beside publish_preview: it runs on every merge to main that touches mobile paths, is signed with UPDATES_SIGNING_KEY, and uploads Sentry source maps.
  • The fingerprint runtime version still blocks an update from any binary whose native layer it doesn't match. On a native change, the update waits for the new binary to clear App Review.
  • update-production.yml stays as a manual lane for republishing outside a merge.
  • RELEASE.md is updated to match.

Trade-off

Every mobile merge reaches all App Store users within minutes, with no approval and no staged rollout. eas update:rollback is the way back. An update that migrates persisted state is still not safe to roll back, so fix forward.

Validation

  • eas workflow:validate .eas/workflows/deploy.yml passes.
  • The first real run will be the merge of this PR (it touches apps/mobile/**). That run publishes current main, including #8480, to production.

Summary by cubic

Merging to main now publishes OTA updates to the production channel automatically, so installed TestFlight and App Store builds keep up with the API and host-service instead of lagging on old JS. The deploy.yml and pr-preview.yml trigger paths now also cover changes to packages/chat and packages/cloud-client.

  • The fingerprint runtime version still keeps an update off any binary whose native layer doesn't match, so native changes wait for the new binary to clear App Review.
  • update-production.yml remains as a manual lane for republishing outside a merge.
  • Every update reaches all production users with no staged rollout; roll back with eas update:rollback.
  • RELEASE.md documents the new flow.

Summary by CodeRabbit

  • New Features
    • Production iOS updates are published automatically after the production fingerprint check, with Sentry sourcemap uploads enabled.
    • Changes under the chat and cloud-client packages now trigger mobile preview and production workflows.
  • Documentation
    • Updated the release guide to explain publishing to preview and production, compatibility requirements, and manual approved republishing outside a merge.