A founding engineer at Posh shares how they rebuilt their mobile CI/CD pipeline using Expo's EAS Workflows, fingerprinting, and Expo Updates to move from manual weekly releases to continuous delivery. The post details five automations: PR previews with QR codes, OTA branches for batching JS-only updates, version branches for native changes, a master workflow orchestrating everything, and Slack/Linear notifications tied to GitHub releases. The result is nearly monthly store releases plus multiple OTA updates per week, with staging gates preventing accidental production deployments.
Table of contents
Discovering our pain-pointsWhat we wanted to solve forPre-requisitesAutomation 1: Setting up PR previewsAutomation 2: OTA branchesAutomation 3: Version branchesAutomation 4: The master workflowAutomation 5: Notifying our teamClosing thoughts19K Impressions