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 12 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.
### Minor Changes - #3389 `922a1c1` Thanks @hpouillot! - Add exception steps to error tracking (aka breadcrumbs) (2026-04-22)
922a1c1 Thanks @hpouillot! - Add exception steps to error tracking (aka breadcrumbs)
(2026-04-22)### Patch Changes - #3426 `1a0b58d` Thanks @marandaneto! - Trim surrounding whitespace from user-provided API keys, personal API keys, and host config
1a0b58d Thanks @marandaneto! - Trim surrounding whitespace from user-provided API keys, personal API keys, and host config values before using them.
(2026-04-21)Your coding agent can read these notes before it upgrades. Set up the MCP server →
### Patch Changes - #3351 `c735b08` Thanks @dmarticus! - Send $device_id as a top-level field in /flags requests so the feature flags service can use
c735b08 Thanks @dmarticus! - Send $device_id as a top-level field in /flags requests so the feature flags service can use it for device-based bucketing during remote evaluation
(2026-04-09)### Patch Changes - #3340 `57ee5b2` Thanks @dmarticus! - Add device bucketing support to the React Native SDK for stable feature flag assignment acros
57ee5b2 Thanks @dmarticus! - Add device bucketing support to the React Native SDK for stable feature flag assignment across identity changes
(2026-04-07)### Minor Changes - #3302 `fc5589f` Thanks @dmarticus! - preserve $set_once semantics in local flag evaluation cache (2026-04-07)
fc5589f Thanks @dmarticus! - preserve $set_once semantics in local flag evaluation cache
(2026-04-07)### Patch Changes - #3320 `a01a3d5` Thanks @dustinbyrne! - fix: send $groupidentify for new groups even when no properties are provided (2026-04-02)
a01a3d5 Thanks @dustinbyrne! - fix: send $groupidentify for new groups even when no properties are provided
(2026-04-02)### Patch Changes - #3309 `197eeda` Thanks @marandaneto! - Extract CLI and sourcemap utilities from @posthog/core into @posthog/plugin-utils to remove
197eeda Thanks @marandaneto! - Extract CLI and sourcemap utilities from @posthog/core into @posthog/plugin-utils to remove cross-spawn from React Native dependencies
(2026-04-01)### Patch Changes - #3296 `a863914` Thanks @marandaneto! - Fix captureException crashing in React Native with ReferenceError: Property 'Event' doesn't
a863914 Thanks @marandaneto! - Fix captureException crashing in React Native with ReferenceError: Property 'Event' doesn't exist
(2026-03-30)### Patch Changes - #3292 `4bdfdbc` Thanks @marandaneto! - Add @default JSDoc tags to PostHogCoreOptions configuration properties for better IDE docum
4bdfdbc Thanks @marandaneto! - Add @default JSDoc tags to PostHogCoreOptions configuration properties for better IDE documentation and discoverability.
(2026-03-27)### Patch Changes - #3286 `8d34289` Thanks @marandaneto! - Use async native CompressionStream for gzip compression to avoid blocking the main thread (
8d34289 Thanks @marandaneto! - Use async native CompressionStream for gzip compression to avoid blocking the main thread
(2026-03-27)### Patch Changes - #3265 `314120a` Thanks @hpouillot! - fix sourcemap upload with stdin, clean config (2026-03-20)
314120a Thanks @hpouillot! - fix sourcemap upload with stdin, clean config
(2026-03-20)### Minor Changes - #3246 `9cd2313` Thanks @hpouillot! - pipe chunk file path to stdin (2026-03-18)
9cd2313 Thanks @hpouillot! - pipe chunk file path to stdin
(2026-03-18)### Patch Changes - #3236 `bc30c2d` Thanks @dustinbyrne! - fix: Clean up leaked timers in edge runtimes (2026-03-13) - #3236 `bc30c2d` Thanks @dustinb
#3236 bc30c2d Thanks @dustinbyrne! - fix: Clean up leaked timers in edge runtimes
(2026-03-13)
#3236 bc30c2d Thanks @dustinbyrne! - Omit the config query parameter by default to request only the necessary data
(2026-03-13)
### Patch Changes - #3220 `4009c15` Thanks @ablaszkiewicz! - add better handling for CustomEvent inside unhandled rejections (2026-03-11)
4009c15 Thanks @ablaszkiewicz! - add better handling for CustomEvent inside unhandled rejections
(2026-03-11)### Patch Changes - #3185 `5e8d5fc` Thanks @marandaneto! - fix: export getRemoteConfigBool, getRemoteConfigNumber, and isValidSampleRate from @posthog
5e8d5fc Thanks @marandaneto! - fix: export getRemoteConfigBool, getRemoteConfigNumber, and isValidSampleRate from @posthog/core
(2026-03-02)### Patch Changes - #3107 `9dbc05e` Thanks @ablaszkiewicz! - warning on manual capture('$exception') (2026-02-18)
9dbc05e Thanks @ablaszkiewicz! - warning on manual capture('$exception')
(2026-02-18)### Minor Changes - #3086 `e962f01` Thanks @marandaneto! - feat: support remote config for error tracking, session replay capture performance and capt
e962f01 Thanks @marandaneto! - feat: support remote config for error tracking, session replay capture performance and capture logs
(2026-02-17)### Minor Changes - #3045 `0acf16f` Thanks @dustinbyrne! - feat: Add getFeatureFlagResult to PostHogCore (2026-02-10)
0acf16f Thanks @dustinbyrne! - feat: Add getFeatureFlagResult to PostHogCore
(2026-02-10)### Minor Changes - #2820 `d578824` Thanks @ordehi! - Add survey response validation for message length (min and max length). Fixes whitespace-only by
### Patch Changes - #3028 `e055f9a` Thanks @marandaneto! - fix: Queue pending feature flags reload instead of dropping requests when a reload is alrea
e055f9a Thanks @marandaneto! - fix: Queue pending feature flags reload instead of dropping requests when a reload is already in flight
(2026-02-09)### Patch Changes - #3039 `8f75dae` Thanks @hpouillot! - fix(err): fix console error capturing (2026-02-06)
8f75dae Thanks @hpouillot! - fix(err): fix console error capturing
(2026-02-06)### Minor Changes - #3023 `bb62809` Thanks @marandaneto! - feat: only capture $set events if the user properties have changed (2026-02-04)
bb62809 Thanks @marandaneto! - feat: only capture $set events if the user properties have changed
(2026-02-04)### Minor Changes - #3009 `c99e5fe` Thanks @marandaneto! - feat: add setPersonProperties method (2026-02-03)
c99e5fe Thanks @marandaneto! - feat: add setPersonProperties method
(2026-02-03)### Minor Changes - #2996 `7768010` Thanks @matheus-vb! - Filter out flags marked as failed before merging with cached values, preventing transient ba
7768010 Thanks @matheus-vb! - Filter out flags marked as failed before merging with cached values, preventing transient backend errors from overwriting previously evaluated flag states
(2026-02-03)### Minor Changes - #2966 `727536c` Thanks @adboio! - support "always" survey schedule (2026-01-29)
### Minor Changes - #2967 `cbe84c1` Thanks @adboio! - support auto-submit on selection for survey rating questions (2026-01-29)
### Minor Changes - #2984 `8c0c495` Thanks @ablaszkiewicz! - include possible pnpm bin path (2026-01-28)
8c0c495 Thanks @ablaszkiewicz! - include possible pnpm bin path
(2026-01-28)### Patch Changes - #2971 `f51560c` Thanks @marandaneto! - fix: groups and groupidentify is a no-op if person profiles is set to never (2026-01-27)
f51560c Thanks @marandaneto! - fix: groups and groupidentify is a no-op if person profiles is set to never
(2026-01-27)### Minor Changes - #2917 `933c763` Thanks @marandaneto! - feat: add support for person_profiles react native, core and web-lite (2026-01-23)
933c763 Thanks @marandaneto! - feat: add support for person_profiles react native, core and web-lite
(2026-01-23)### Minor Changes - #2882 `8a5a3d5` Thanks @adboio! - add support for question prefill in popover surveys, add useThumbSurvey hook (2026-01-20)
Updated dependencies [`88f8655`]:
88f8655 Thanks @turnipdabeets! - Fail webpack, Next.js webpack, and Nuxt builds when PostHog cannot process or upload source maps; set sourcemaps.failOnError: false to log the error and continue the build instead.
(2026-10-23)88f8655]:
#2897 b7fa003 Thanks @matheus-vb! - Add $feature_flag_error to $feature_flag_called events to track flag evaluation failures
(2026-01-20)
#2931 f0cbc0d Thanks @marandaneto! - chore: before_send support for web lite and react native
(2026-01-20)
event mode requires a posthog-cli with release resolve and --release-mode , and posthog-js 1.409.0, posthog-node 5.47.0, or @posthog/core 1.46.0 at ru
#4705 dd5888a Thanks @ablaszkiewicz! - Change the default sourcemaps.releaseMode to event: set sourcemaps.releaseMode: 'symbol-set', or POSTHOG_RELEASE_MODE=symbol-set, to keep binding uploaded symbol sets to a release. The @posthog/plugin-utils bump is major, so an installed plugin keeps the old default until the plugin itself is upgraded.
event mode requires a posthog-cli with release resolve and --release-mode, and posthog-js 1.409.0, posthog-node 5.47.0, or @posthog/core 1.46.0 at runtime. An older CLI fails a rollup build and skips the upload on webpack and Next.js. An older SDK reports no release on exceptions. (2026-09-02)
c589ab8 Thanks @cat-ph! - Bump @posthog/cli to ~0.16.2, which fixes a race in sourcemap process: inject and upload used to walk the directory roots separately, so a bundler still writing into the output directory mid-run (e.g. Turbopack's background filesystem-cache flush on Next.js 16.3+) could hand upload a chunk inject never stamped and abort the build with "Chunk ID not found". The CLI now uploads exactly the pairs it injected, and --delete-after cleanup skips files that vanished or changed after upload instead of failing the build.c589ab8, dd5888a]:
#2900 23770e9 Thanks @dmarticus! - Renamed evaluationEnvironments to evaluationContexts for clearer semantics. The term "contexts" better reflects that this feature is for specifying evaluation contexts (e.g., "web", "mobile", "checkout") rather than deployment environments (e.g., "staging", "production").
posthog.init option evaluationEnvironments is now deprecated in favor of evaluationContexts. The old property will continue to work and will log a deprecation warning. It will be removed in a future major version.// Before
posthog.init('<ph_project_api_key>', {
evaluationEnvironments: ['production', 'web', 'checkout'],
})
// After
posthog.init('<ph_project_api_key>', {
evaluationContexts: ['production', 'web', 'checkout'],
})
``` (2026-01-19)
#2593 fba9fb2 Thanks @daibhin! - track LLMA trace_id on exceptions and exception_id on traces
(2026-01-08)
#2856 c1ed63b Thanks @marandaneto! - chore: expose default stack parser creator
(2026-01-08)
b676b4d Thanks @lucasheriques! - feat: allow customizing text colors on web and react native
(2025-12-22)6b0aabf Thanks @marandaneto! - chore: move the user-agent-utils from the browser to the core package
(2025-12-17)#2690 e9c00fd Thanks @robbie-c! - Related to https://www.wiz.io/blog/critical-vulnerability-in-react-cve-2025-55182
We didn't include any of the vulnerable deps in any of our packages, however we did have them as dev / test / example project dependencies.
There was no way that any of these vulnerable packages were included in any of our published packages.
We've now patched out those dependencies.
Out of an abundance of caution, let's create a new release of all of our packages. (2025-12-04)
e1617d9 Thanks @dmarticus! - add $feature_flag_evaluated_at properties to $feature_flag_called events
(2025-12-03)86dab38 Thanks @hpouillot! - package deprecation
(2025-11-24)3eed1a4 Thanks @marandaneto! - last version was compromised
(2025-11-24)83f5d07 Thanks @hpouillot! - export logger creation
(2025-11-20)c242702 Thanks @hpouillot! - export log level type
(2025-11-20)8acd88f Thanks @hpouillot! - fix frame platform property for $exception events
(2025-11-19)87f9604 Thanks @hpouillot! - expose binary path resolutiond8d98c9 Thanks @hpouillot! - escape cli args and path in shell mode068d55e Thanks @lricoy! - Add bot pageview collection behind preview flag. Enables tracking bot traffic as $bot_pageview events when the __preview_capture_bot_pageviews flag is enabled.751b440 Thanks @pauldambra! - fix: bucketed rate limiter can calculate tokens without a timere0a6fe0 Thanks @hpouillot! - remove some export from main core#2417 daf919b Thanks @dmarticus! - feat: Add evaluation environments support for feature flags
This PR adds base support for evaluation environments in the core library, allowing SDKs that extend the core to specify which environment tags their SDK instance should use when evaluating feature flags.
The core library now handles sending the evaluation_environments parameter to the feature flags API when configured.
7d45a7a Thanks @marandaneto! - fix: remove deprecated attribute $exception_personURL from exception events10da2ee Thanks @ablaszkiewicz! - move binary calling logic to core packagee19a384 Thanks @hpouillot! - create a common logger for node and react-native5820942 Thanks @hpouillot! - remove testing exportcaecb94 Thanks @hpouillot! - update error properties builderac48d8f Thanks @hpouillot! - chore: align js syntax with package supportda07e41 Thanks @hpouillot! - add error tracking processing1981815 Thanks @hpouillot! - add promise queueNothing published for this version
## 1.9.1 ### Patch Changes - #5664 `a7485da` Thanks @ioannisj! - Bump @posthog/cli to 0.19.1 so builds outside a git checkout that set only a release
Updated dependencies [`096131d`, `34833f2`]:
e4df2d5 Thanks @pauldambra! - Add optional server request context and access to the existing server client for OpenTelemetry span enrichment.
(2026-10-28)## 1.8.1 ### Patch Changes - #5664 `a7485da` Thanks @ioannisj! - Bump @posthog/cli to 0.19.1 so builds outside a git checkout that set only a release
## 1.8.0 ### Minor Changes - #5398 `88f8655` Thanks @turnipdabeets! - Fail webpack, Next.js webpack, and Nuxt builds when PostHog cannot process or up
88f8655 Thanks @turnipdabeets! - Fail webpack, Next.js webpack, and Nuxt builds when PostHog cannot process or upload source maps; set sourcemaps.failOnError: false to log the error and continue the build instead.
(2026-10-23)Nothing published for this version
event mode requires a posthog-cli with release resolve and --release-mode , and posthog-js 1.409.0, posthog-node 5.47.0, or @posthog/core 1.46.0 at ru
#4705 dd5888a Thanks @ablaszkiewicz! - Change the default sourcemaps.releaseMode to event: set sourcemaps.releaseMode: 'symbol-set', or POSTHOG_RELEASE_MODE=symbol-set, to keep binding uploaded symbol sets to a release. The @posthog/plugin-utils bump is major, so an installed plugin keeps the old default until the plugin itself is upgraded.
event mode requires a posthog-cli with release resolve and --release-mode, and posthog-js 1.409.0, posthog-node 5.47.0, or @posthog/core 1.46.0 at runtime. An older CLI fails a rollup build and skips the upload on webpack and Next.js. An older SDK reports no release on exceptions. (2026-09-02)
c589ab8 Thanks @cat-ph! - Bump @posthog/cli to ~0.16.2, which fixes a race in sourcemap process: inject and upload used to walk the directory roots separately, so a bundler still writing into the output directory mid-run (e.g. Turbopack's background filesystem-cache flush on Next.js 16.3+) could hand upload a chunk inject never stamped and abort the build with "Chunk ID not found". The CLI now uploads exactly the pairs it injected, and --delete-after cleanup skips files that vanished or changed after upload instead of failing the build.dd5888a]:
event mode requires a posthog-cli with release resolve and --release-mode , and posthog-js 1.409.0, posthog-node 5.47.0, or @posthog/core 1.46.0 at ru
#4705 dd5888a Thanks @ablaszkiewicz! - Change the default sourcemaps.releaseMode to event: set sourcemaps.releaseMode: 'symbol-set', or POSTHOG_RELEASE_MODE=symbol-set, to keep binding uploaded symbol sets to a release. The @posthog/plugin-utils bump is major, so an installed plugin keeps the old default until the plugin itself is upgraded.
event mode requires a posthog-cli with release resolve and --release-mode, and posthog-js 1.409.0, posthog-node 5.47.0, or @posthog/core 1.46.0 at runtime. An older CLI fails a rollup build and skips the upload on webpack and Next.js. An older SDK reports no release on exceptions. (2026-09-02)
c589ab8 Thanks @cat-ph! - Bump @posthog/cli to ~0.16.2, which fixes a race in sourcemap process: inject and upload used to walk the directory roots separately, so a bundler still writing into the output directory mid-run (e.g. Turbopack's background filesystem-cache flush on Next.js 16.3+) could hand upload a chunk inject never stamped and abort the build with "Chunk ID not found". The CLI now uploads exactly the pairs it injected, and --delete-after cleanup skips files that vanished or changed after upload instead of failing the build.dd5888a]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The token is no longer left on transport.sessionId after the response. Host code that read it there should read the Mcp-Session-Id header the client r
#5732 5e5cb86 Thanks @lucasheriques! - Fix stateless servers on @modelcontextprotocol/server 2.0 to 2.2 that reuse one transport for every client: the session token minted at initialize now rides only that client's initialize response. Before, it stayed on the transport, so every later client's initialize failed with 400 "Server already initialized" and later responses handed the first client's token to other clients. Per-request and multi-pod stateless servers still get a stable session token.
The token is no longer left on transport.sessionId after the response. Host code that read it there should read the Mcp-Session-Id header the client replays instead. (2026-11-13)
Updated dependencies [`22f3f71`]:
22f3f71 Thanks @lucasheriques! - fix(mcp): keep the thrown value on high-level McpServer tool calls, so $mcp_error_type and $mcp_error_status reflect what the tool threw. This covers MCP SDK v2, a thrown value that is not an Error, and servers built per request that share tool functions. For a thrown non-Error, $mcp_error_message and error grouping now describe the thrown value (for example 'UpstreamError' captured as exception with message: 'bad') instead of [object Object]. $mcp_error_type is now redacted like the message, including an errorType passed to captureToolCall. An error whose getters throw while it is captured is still recorded: a tool call falls back to the tool result, and other events record Unknown error instead of being dropped.
(2026-11-12)22f3f71]:
## 1.2.0 ### Minor Changes - #5671 `4a30932` Thanks @lucasheriques! - A failed tool call now sets $mcp_error_status to the HTTP status behind it, read
4a30932 Thanks @lucasheriques! - A failed tool call now sets $mcp_error_status to the HTTP status behind it, read from the thrown error or its cause chain (status_code, statusCode or status, on the error or its response, as a fetch Response, axios and got carry it). Failures from an upstream API now group by status in MCP Analytics instead of landing in "unknown".
(2026-11-12)8f5e876 Thanks @DanielVisca! - Ignore non-string name/version values returned by the clientInfo option instead of recording them as the MCP client.
(2026-11-12)Updated dependencies [`fb313fe`, `fee9bee`, `fee9bee`]:
4d0681f Thanks @DanielVisca! - feat: add sessionId and clientInfo options so stateless per-request servers can supply the session id and client name for each request
(2026-11-10)Nothing published for this version
Updated dependencies [`fac34e4`, `bfbaff7`]:
fac34e4 Thanks @lucasheriques! - Fix intent and payload capture bugs: a long digit run no longer drops $mcp_intent with a stack overflow (card redaction is otherwise unchanged), captured tool arguments are limited before they are sanitized and credential-named arguments are not walked, and $mcp_feedback_<name> object extras redact identifiers in keys and numbers. A parsed __proto__ argument is still dropped, as before.
(2026-11-09)fac34e4, bfbaff7]:
## 1.0.0 ### Major Changes - #5584 `650e968` Thanks @lucasheriques! - Release 1.0.0. The API and the $mcp_* events are now stable: a minor or patch re
650e968 Thanks @lucasheriques! - Release 1.0.0. The API and the $mcp_* events are now stable: a minor or patch release no longer renames or removes an event or property, changes its type, or changes which requests send an event, so your saved insights keep working across upgrades. New events and properties can still arrive in minor releases. Upgrading from 0.x needs no code change.
(2026-11-06)One column per month.