Skip to content

armgit / macro

Public Imported from GitHub
0

Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.

fix(ios): prompt installs older than 2.0.11 to update from the App Store (#8596)

Peter Chinmanbef3e5bcd81a
diff --git a/apps/web/min-native-build.json b/apps/web/min-native-build.json
index fa56e299f2..61e227bca2 100644
--- a/apps/web/min-native-build.json
+++ b/apps/web/min-native-build.json
@@ -1,4 +1,4 @@
{
"android": 1,
- "ios": 185
+ "ios": 190
}
diff --git a/docs/architecture/email.md b/docs/architecture/email.md
index 5ed3a27a6a..6d30dc235e 100644
--- a/docs/architecture/email.md
+++ b/docs/architecture/email.md
@@ -585,8 +585,8 @@ completed attachments, both providers, and server sends from other devices befor
release. The separate cache-bootstrap recovery hotfix remains useful
for draft synchronization and does not determine send availability.
-The approved iOS 2.0.11 build 190 is held for manual release with the production
-deployment. Its source is `04063d2bb35d7369eae93900c2692f3ecccf882b`.
+iOS 2.0.11 build 190 was released with the production rollout on 2026-10-22.
+Its source is `04063d2bb35d7369eae93900c2692f3ecccf882b`.
The subsequent main merge through `93900478fb` preserves its native/web and
email interfaces. Build 190 keeps its compiled format-3 native cache; the new
format-4 compression in cache version 0.6.52 belongs to the cache engine, and
@@ -594,11 +594,9 @@ only JSON crosses the native/web boundary. Browser OPFS storage is separate.
New native diagnostics are optional, and the agent runtime/Chromium additions
are desktop-only. The `skip-ios-update` exception records this compatibility
review, not identical build provenance.
-Keep the iOS floor at 185. Deploy the migrations and generation-aware backend
-writers before the frontend, then release the approved App Store version as
-part of that production rollout. Do not release it early: its embedded frontend
-also requires those backend changes. Recheck compatibility if further native
-requirements are introduced before deployment.
+Older iOS builds therefore remain compatible with the outbox; the iOS floor is
+190 only so that the next production deploy prompts them to update from the
+App Store.
The format-4 browser cache starts a separate physical database. Old nonempty
general mutation queues are retained but are not imported into it; verify their