Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

chore(mobile): request the 1.8.0 native release (#127544)

Chris Volzer0e01b0c178be
diff --git a/products/mobile/app.config.ts b/products/mobile/app.config.ts
index 27a7b08a2458..5debd5ee0076 100644
--- a/products/mobile/app.config.ts
+++ b/products/mobile/app.config.ts
@@ -59,7 +59,7 @@ export default ({ config, projectRoot }: ConfigContext): ExpoConfig => {
slug: 'posthog',
owner: 'posthog',
scheme,
- version: '1.7.0',
+ version: '1.8.0',
orientation: 'portrait',
userInterfaceStyle: 'automatic',
icon: icons.png,
diff --git a/products/mobile/docs/OTA.md b/products/mobile/docs/OTA.md
index 29e4d51aa1d6..1521d8b042f5 100644
--- a/products/mobile/docs/OTA.md
+++ b/products/mobile/docs/OTA.md
@@ -43,7 +43,7 @@ Do not run `pnpm update`. That is pnpm's own command, and it upgrades dependenci
## Runtime version
-`app.config.ts` sets `runtimeVersion.policy` to `appVersion`, so the runtime version equals `version` (now `1.7.0`).
+`app.config.ts` sets `runtimeVersion.policy` to `appVersion`, so the runtime version equals `version` (now `1.8.0`).
An update reaches only the builds with the same runtime version.
The device's `appVersion` policy does not detect native changes. The hosted release workflow additionally compares Expo native fingerprints for both platforms against the last successful native release. You must raise `version` and request a native release when a change needs native code, for example:
diff --git a/products/mobile/docs/RELEASING.md b/products/mobile/docs/RELEASING.md
index e90c0820db5b..546da32a3f68 100644
--- a/products/mobile/docs/RELEASING.md
+++ b/products/mobile/docs/RELEASING.md
@@ -96,6 +96,12 @@ Version `1.6.0` follows `native-150` through the `native-160` native release req
It includes full-screen chats with Back, New chat, Copy link to chat and Archive chat controls, readable insight-table numbers with horizontal scrolling, and safer release retries.
It targets TestFlight and Google Play internal testing and establishes a new runtime for compatible OTA updates.
+Version `1.8.0` requests a new native release through `native-180`, following the last completed release, `native-160`.
+The earlier report-fix OTA and `native-170` requests remain historical because neither created a release receipt.
+This release uses the updated hosted workflow and includes the report chart, Android verdict scrolling and inbox cache fixes already on `master`.
+It submits to TestFlight and Google Play internal testing. Add the submitted builds to the existing external testing tracks separately.
+Publish an OTA for the `1.8.0` runtime only after the native release receipt completes.
+
The native receipt records the certificate fingerprint. An OTA request must match it as well as the native fingerprints; a receipt without a certificate fingerprint cannot authorize an OTA.
Rotate the key and certificate together, retain the old material securely for older runtimes, and raise the app version in a new native release before publishing updates with the new key.
diff --git a/products/mobile/releases/requests/native-180.json b/products/mobile/releases/requests/native-180.json
new file mode 100644
index 000000000000..9ec0c0c02078
--- /dev/null
+++ b/products/mobile/releases/requests/native-180.json
@@ -0,0 +1,8 @@
+{
+ "schemaVersion": 1,
+ "id": "native-180",
+ "kind": "native",
+ "runtimeVersion": "1.8.0",
+ "previousRelease": "native-160",
+ "notes": "This release includes formula charts in report summaries and details, Android scrolling fixes for long verdicts, and inbox cache validation. Test sign-in, report charts, verdict scrolling, inbox refresh and pagination, and chats on iOS and Android."
+}