NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3291 most downloaded on npm
Latest stable
1.67.1
Last release 9 days ago
10 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
1 years old
239 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
### Patch Changes - #3828 `8464c92` Thanks @turnipdabeets! - fix: persist the session replay config from a /flags response before emitting the feature
8464c92 Thanks @turnipdabeets! - fix: persist the session replay config from a /flags response before emitting the featureflags event, so listeners (e.g. React Native session replay linked-flag re-evaluation) read a recording config consistent with the new flag values. This only reorders two adjacent synchronous writes in the stateful core client (used by posthog-react-native and @posthog/web); the event payload is unchanged, and posthog-node and the browser posthog-js package do not use this code path.
(2026-06-15)Updated dependencies [`29bf8e3`]:
29bf8e3 Thanks @marandaneto! - Add missing bugs metadata to package manifests.
(2026-06-15)29bf8e3]:
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Updated dependencies [`dbf2377`]:
dbf2377]:
### Patch Changes - #3799 `25822ac` Thanks @turnipdabeets! - fix(logs): when a logs beforeSend hook throws, log the error and drop the record (fail cl
25822ac Thanks @turnipdabeets! - fix(logs): when a logs beforeSend hook throws, log the error and drop the record (fail closed) instead of continuing the chain and enqueuing it — a buggy redaction hook must not leak an unredacted log record.
(2026-06-11)### Patch Changes - Updated dependencies []: - @posthog/types@1.386.1
Renders a "Back" button on web surveys after the first question. Default is off — existing surveys are unchanged. Uses a visited-index history stack s
#3634 612f97a Thanks @lucasheriques! - feat(surveys): add opt-in appearance.allowGoBack for multi-question surveys, and make button labels translatable
Renders a "Back" button on web surveys after the first question. Default is off — existing surveys are unchanged. Uses a visited-index history stack so back-navigation respects branching paths (response_based, specific_question), and abandoned-branch responses are pruned before submission so analytics aren't polluted. Returning to a question pre-fills the prior answer. appearance.backButtonText overrides the default label. The button uses the survey's text color so it stays readable on any background, and it also shows in survey previews.
Also adds submitButtonText and backButtonText to survey-level translations, so both the submit and back button labels can be localized via appearance translations (previously only the per-question button text was translatable). (2026-06-10)
Updated dependencies [`c11794d`, `f601c49`]:
Updated dependencies [`2d21ada`]:
2d21ada]:
Updated dependencies [`d9462b3`]:
d9462b3]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.384.1
Note: $browser_version for Google Search App is not comparable across platforms — iOS yields a version like 284.0 (from GSA/284.0.564099828) while And
#3782 0c2acb9 Thanks @pauldambra! - Detect the Google Search App (GSA) as its own $browser value (Google Search App) via the cross-platform GSA/ UA marker, instead of reporting the embedded webview as Mobile Safari (iOS) or Chrome (Android). Gated behind the new detect_google_search_app config option, which the 2026-05-30 config defaults opt into automatically — left off otherwise to keep existing browser attribution backwards-compatible.
Note: $browser_version for Google Search App is not comparable across platforms — iOS yields a version like 284.0 (from GSA/284.0.564099828) while Android yields a version like 14.21 (from GSA/14.21.20.28.arm64), since Google maintains separate versioning schemes for the two apps. Avoid building cross-platform version dashboards on $browser_version for this browser. (2026-06-10)
0c2acb9]:
Updated dependencies [`783ba46`]:
783ba46]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.383.2
### Patch Changes - Updated dependencies []: - @posthog/types@1.383.1
Updated dependencies [`227c9b0`, `393f9e2`]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.382.0
Updated dependencies [`a7bd828`]:
a7bd828]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.380.1
Updated dependencies [`2387084`]:
2387084]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.379.3
### Patch Changes - Updated dependencies []: - @posthog/types@1.379.2
### Patch Changes - Updated dependencies []: - @posthog/types@1.379.1
### Patch Changes - Updated dependencies []: - @posthog/types@1.379.0
### Patch Changes - Updated dependencies []: - @posthog/types@1.378.1
Updated dependencies [`8181354`]:
8181354]:
detectBrowser / detectBrowserVersion now accept an optional third argument, BrowserDetectionHints, with a brave flag (set when navigator.brave exists)
#3708 3d4a76f Thanks @pauldambra! - Detect Brave (desktop, Android, iOS), Vivaldi, Yandex, Naver Whale, DuckDuckGo, Pale Moon, and Waterfox so users on these browsers no longer get bucketed as Chrome or Firefox.
detectBrowser / detectBrowserVersion now accept an optional third argument, BrowserDetectionHints, with a brave flag (set when navigator.brave exists). The browser SDK populates this automatically to catch desktop / Android Brave, which is Chromium-based and carries no UA marker. Brave on iOS is picked up purely from the Brave/ UA marker — WebKit doesn't ship navigator.brave. The original two-argument signature still works for non-DOM callers. (2026-06-01)
### Patch Changes - Updated dependencies []: - @posthog/types@1.376.6
### Patch Changes - #3694 `d9ad199` Thanks @gustavohstrassburger! - fix(react-native): preserve non-string property types (booleans, arrays, numbers,
d9ad199 Thanks @gustavohstrassburger! - fix(react-native): preserve non-string property types (booleans, arrays, numbers, objects) when caching person and group properties for feature flag evaluation. Previously these were force-coerced to strings via String(value), causing flag conditions using boolean equality or array contains to fail on device while the PostHog UI still evaluated correctly.
(2026-05-31)### Patch Changes - #3681 `7b84b75` Thanks @ablaszkiewicz! - unify captureException in posthog core (2026-05-28) - Updated dependencies []: - @posthog
7b84b75 Thanks @ablaszkiewicz! - unify captureException in posthog core
(2026-05-28)### Patch Changes - Updated dependencies []: - @posthog/types@1.376.3
### Patch Changes - Updated dependencies []: - @posthog/types@1.376.2
### Patch Changes - #3665 `5568f12` Thanks @ioannisj! - Don't autocapture PostHog's own PostHogFetchNetworkError (raised when the device is offline) a
5568f12 Thanks @ioannisj! - Don't autocapture PostHog's own PostHogFetchNetworkError (raised when the device is offline) as a $exception. These connectivity failures are expected and were flooding error tracking with internal SDK noise. Adds an isPostHogFetchNetworkError type guard to @posthog/core so SDKs can detect these errors.
(2026-05-26)### Patch Changes - #3639 `c806cca` Thanks @marandaneto! - Use native async gzip compression for session recording events when CompressionStream is av
c806cca Thanks @marandaneto! - Use native async gzip compression for session recording events when CompressionStream is available.
(2026-05-22)Updated dependencies [`2e1d5f4`]:
2e1d5f4]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.374.4
Updated dependencies [`557b893`]:
a880dbc Thanks @Ashut0sh-mishra! - Detect Oculus Browser (Meta Quest headsets) correctly instead of falling back to Chrome
(2026-05-20)557b893]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.374.2
### Patch Changes - Updated dependencies []: - @posthog/types@1.374.1
Updated dependencies [`594ea11`]:
594ea11]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.373.5
### Patch Changes - #3602 `4b895bf` Thanks @marandaneto! - Validate gzip request bodies at the browser send boundary and fall back to JSON if the outg
4b895bf Thanks @marandaneto! - Validate gzip request bodies at the browser send boundary and fall back to JSON if the outgoing body is not gzip data.
(2026-05-12)### Minor Changes - #3599 `ad60818` Thanks @turnipdabeets! - Expose UUID and cookie helpers from @posthog/core and posthog-node for users managing dis
ad60818 Thanks @turnipdabeets! - Expose UUID and cookie helpers from @posthog/core and posthog-node for users managing distinct_id outside the browser SDK (e.g. Lambda functions handing out cross-domain redirects). The helpers were already implemented in @posthog/next — this change lifts them to core so all SDKs can re-use them. @posthog/next now re-exports the same surface from @posthog/core to keep existing consumers working without churn. Closes #2143.
(2026-05-12)### Patch Changes - #3568 `223d925` Thanks @marandaneto! - Validate native gzip output before sending requests and fall back when CompressionStream re
223d925 Thanks @marandaneto! - Validate native gzip output before sending requests and fall back when CompressionStream returns malformed data.
(2026-05-11)### Patch Changes - Updated dependencies []: - @posthog/types@1.373.1
Updated dependencies [`4c0c7d9`, `0a835fa`]:
### Patch Changes - Updated dependencies []: - @posthog/types@1.372.10
### Patch Changes - Updated dependencies []: - @posthog/types@1.372.9
### Patch Changes - #3516 `220cd61` Thanks @marandaneto! - fix: consume fetch response body to prevent CF Workers runtime warnings (2026-05-04) - #351
#3516 220cd61 Thanks @marandaneto! - fix: consume fetch response body to prevent CF Workers runtime warnings
(2026-05-04)
#3515 255b273 Thanks @marandaneto! - Gate survey translation logs behind SDK debug logging to avoid production console spam.
(2026-05-04)
Updated dependencies []:
### Patch Changes - #3512 `8aee3d5` Thanks @marandaneto! - Do not crash when the React Native SDK is initialized without an API key; initialize as dis
8aee3d5 Thanks @marandaneto! - Do not crash when the React Native SDK is initialized without an API key; initialize as disabled and log an error instead. Disabled clients now also skip manual reload/flush/survey/log network calls.
(2026-05-04)Manual capture is unconditional — calling the API ships records, matching the events pipeline's manual capture() shape. Only blockers: optedOut, missi
#3492 cf56753 Thanks @lucasheriques! - Add translated survey rendering support in React Native and share survey translation logic through @posthog/core.
(2026-05-01)
#3480 04db756 Thanks @turnipdabeets! - Add manual log capture API for React Native: posthog.captureLog(), posthog.logger.{trace,debug,info,warn,error,fatal}(), posthog.flushLogs(), and a logs config option on the constructor. Records ship to PostHog's logs product (/i/v1/logs) in OTLP format, batched on a timer / AppState change / buffer fill, and persisted to a dedicated logs-storage file.
Manual capture is unconditional — calling the API ships records, matching the events pipeline's manual capture() shape. Only blockers: optedOut, missing/empty body, and missing API key. The wire field response.logs.captureConsoleLogs is browser-only (it gates the JS SDK's console.* autocapture extension) and is not read by RN. When console autocapture lands on RN as a follow-up, that PR will introduce a local opt-in for the autocapture path specifically; manual capture will remain unconditional. (2026-05-01)
### Patch Changes - Updated dependencies []: - @posthog/types@1.372.5
### Patch Changes - Updated dependencies []: - @posthog/types@1.372.4
### Patch Changes - Updated dependencies []: - @posthog/types@1.372.3
### Patch Changes - Updated dependencies []: - @posthog/types@1.372.2
### Patch Changes - #3464 `70508df` Thanks @dustinbyrne! - Avoid using Blob.stream() for native async gzip compression to prevent Safari NotReadableEr
70508df Thanks @dustinbyrne! - Avoid using Blob.stream() for native async gzip compression to prevent Safari NotReadableError stream failures.
(2026-04-24)### Patch Changes - Updated dependencies []: - @posthog/types@1.372.0
### Patch Changes - Updated dependencies []: - @posthog/types@1.371.4
### Patch Changes - #3437 `daf028d` Thanks @dustinbyrne! - Disable the core client instead of throwing when the API key is missing, blank, or invalid.
daf028d Thanks @dustinbyrne! - Disable the core client instead of throwing when the API key is missing, blank, or invalid.
(2026-04-24)Updated dependencies [`96f19b7`]:
96f19b7 Thanks @turnipdabeets! - Lift OTLP log serialization helpers from posthog-js into @posthog/core so the
upcoming React Native logs feature consumes the same builders. Browser gains
two fixes as a side effect: NaN and ±Infinity attribute values no longer get
silently dropped during JSON encoding, and the scope.version OTLP field is
now populated with the SDK version (changes the server's instrumentation_scope
column from "posthog-js@" to "posthog-js@<semver>"). (2026-04-23)96f19b7]:
Also exposes patchFetchForTracingHeaders from @posthog/core so non-browser SDKs can reuse the implementation. (2026-04-23)
#3432 1a8b727 Thanks @richardsolomou! - refactor: rename __add_tracing_headers to addTracingHeaders. The __ prefix signalled an internal/experimental option, but the config is a public API (documented for linking LLM traces to session replays). __add_tracing_headers continues to work as a deprecated alias on the browser SDK.
Also exposes patchFetchForTracingHeaders from @posthog/core so non-browser SDKs can reuse the implementation. (2026-04-23)
One column per month.