: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.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
chore(mobile): request the first hosted native release (#125822)
Chris Volzeraa3b9bee022a
diff --git a/products/mobile/app.config.ts b/products/mobile/app.config.tsindex 1d1612359e7c..51113ad267ac 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.4.0',+ version: '1.5.0',orientation: 'portrait',userInterfaceStyle: 'automatic',icon: icons.png,diff --git a/products/mobile/docs/RELEASING.md b/products/mobile/docs/RELEASING.mdindex 3b9d73b8134c..78e6ddd46fc1 100644--- a/products/mobile/docs/RELEASING.md+++ b/products/mobile/docs/RELEASING.md@@ -87,6 +87,9 @@ Only an approved OTA publishing step writes the private key to an owner-readableStaging and promotion both pass the key to EAS, which signs the manifests locally. The native client verifies updates against its embedded certificate before applying them.The first signed release must be **native**, with a version above the unsigned `1.4.0` baseline. Existing unsigned binaries must upgrade through TestFlight or the stores; this change cannot add verification to them through OTA.++Version `1.5.0` establishes that signed native baseline through the `native-150` release request.+It targets TestFlight and Google Play internal testing. Compatible OTA requests can follow only after its hosted release receipt is complete.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-150.json b/products/mobile/releases/requests/native-150.jsonnew file mode 100644index 000000000000..fb128f915fbe--- /dev/null+++ b/products/mobile/releases/requests/native-150.json@@ -0,0 +1,8 @@+{+ "schemaVersion": 1,+ "id": "native-150",+ "kind": "native",+ "runtimeVersion": "1.5.0",+ "previousRelease": null,+ "notes": "First hosted release of PostHog Mobile. Verify sign-in, project switching, report triage, chats, saved views, push notifications, and the hedgehog widget on iOS and Android."+}