Automate production mobile EAS releases - #5609
Conversation
- Trigger production builds and fingerprint-gated OTA updates on relevant merges - Serialize runs and retain workflow dispatch for manual overrides
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
ApprovabilityVerdict: Needs human review This PR automates production mobile releases (store submissions and OTA updates) on every main merge. Production deployment automation of this scope warrants human review to verify the intended release workflow and safeguards. You can customize Macroscope's approvability policy. Learn more. |
- Add advisory fingerprint comparison for iOS and Android - Label PRs that require a new native build before OTA updates
- Separate fingerprint comparison from PR label management - Use GitHub API labeling for same-repository PRs while keeping fork checks advisory
- Track asset and script changes in mobile release workflows - Keep production builds attached to serialized runs - Use EAS fingerprint commands and fingerprint-hash matching
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
Bugbot Autofix is ON, but a cloud agent failed to start.
Reviewed by Cursor Bugbot for commit a9437f3. Configure here.
- Continue checking both platforms after a build failure - Fail the workflow after recording the platform-specific error
## What's Changed * Move project settings to contextual project routes by @juliusmarminge in pingdotgg/t3code#5923 * Retain thread sidebar data when navigating to /settings so back navigation is instant by @juliusmarminge in pingdotgg/t3code#5930 * Automate production mobile EAS releases by @juliusmarminge in pingdotgg/t3code#5609 * Add settings and usage breadcrumbs by @juliusmarminge in pingdotgg/t3code#5929 * fix(web): correct model picker trigger padding by @Chrono-byte in pingdotgg/t3code#5935 * fix(web): show worktree icon in sidebar v2 by @tris203 in pingdotgg/t3code#5909 * fix(web): enable restore defaults after theme mix changes by @Lucenx9 in pingdotgg/t3code#5928 * fix(web): trait menu closes after you pick a level by @t3dotgg in pingdotgg/t3code#5879 * fix(web): align project name with headline by @carterwsmith in pingdotgg/t3code#5864 * fix(web): update pills use readable theme foregrounds by @chrisdeeming in pingdotgg/t3code#5938 ## New Contributors * @carterwsmith made their first contribution in pingdotgg/t3code#5864 **Full Changelog**: pingdotgg/t3code@v0.0.33-nightly.20260810.1054...v0.0.33-nightly.20260810.1055 Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.33-nightly.20260810.1055
pingdotgg#5609 also added mobile-fingerprint-check.yml, which landed without a conflict and so was never inspected. It runs on blacksmith-8vcpu-ubuntu-2404, which this fork does not have, and it triggers on every pull request touching apps/mobile, packages/client-runtime, packages/contracts, packages/shared, assets or scripts. Its "Native fingerprint diff" check was already sitting queued on this very PR and would never have reported — a permanently pending check, and a blocked merge wherever branch protection waits on all of them. Same fix as #386 for web-preview.yml: GitHub-hosted runners, which is what every other fork workflow uses. There are now no Blacksmith references left in .github/workflows. Also drops the EllipsisIcon import the Sidebar conflict union left behind; the project row's button is SettingsIcon after pingdotgg#5923. Found by the grok-4.5 adversarial review. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

What Changed
main.0.0.32to0.0.31.Why
This makes mobile production releases follow merges automatically while avoiding duplicate builds and incompatible OTA updates. Store builds are created when the app version changes, and JavaScript updates are published only when an installed native binary can apply them. Manual workflow dispatch remains available for retries and forced releases.
Checklist
Note
Medium Risk
Changes production release automation (store submits and OTA channel) on every qualifying merge; misconfigured version or fingerprint logic could skip OTAs or trigger duplicate builds, though serialization and gating reduce blast radius.
Overview
Production mobile releases now run automatically when relevant paths merge to
main, whileworkflow_dispatchstays for manual build/OTA retries.mobile-eas-production.ymladds path-filteredpushtriggers and a serialized concurrency group so OTAs stay ordered (bursts collapse to the latest commit). On push it comparesapp.config.tsversion to the latest EAS production build per platform and starts auto-submit store builds when they differ (in-progress builds count, avoiding duplicates). It then fingerprint-gates production OTAs: updates publish only if a finished build matches the current native fingerprint; otherwise the job summary warns and skips.A new
mobile-fingerprint-check.ymlruns on PRs, fingerprints merge-result vs base (withpnpm installon base for lockfile accuracy), writes an iOS/Android diff to the job summary, and syncs a 📱 Native Change label on in-repo PRs so native drift is visible before merge. The check is advisory and always passes.Reviewed by Cursor Bugbot for commit 88c9273. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Automate production mobile EAS releases and fingerprint checks on push to main
maintouching mobile paths, mobile-eas-production.yml checks the current app version against the latest production build per platform and triggers a new store build + auto-submit if versions differ.📱 Native Changelabel on same-repo PRs.workflow_dispatchtriggers retain the existing build/submit and OTA publish steps unchanged.Macroscope summarized 88c9273.