Posthog Release Notes

1.418.6

Patch Changes

• #4578 bae46bf Thanks @marandaneto! - Drop events when a before-send hook throws instead of sending the unmodified event.

• (2026-08-20)

• #4582 aef2f49 Thanks @ablaszkiewicz! - Stop building a stack frame for a window.onerror report that carries no code position, such as the ResizeObserver loop warning. The frame named the document URL rather than a script, so no source map could resolve it. These exceptions now arrive with no stack trace.

• (2026-08-20)

Updated dependencies [bae46bf, aef2f49]:

• @posthog/[email protected]

1.418.4

Patch Changes

• #4309 b564d61 Thanks @posthog! - Fix session recording in the full browser bundles. array.full.js and module.full.es.js only inlined rrweb, so they still fetched the recorder script at runtime - the request the full bundles exist to avoid. They now inline the whole recorder. Also flags the session with $sdk_debug_recording_script_not_loaded when the recorder script fails to load, so a blocked recorder is visible in analytics rather than only in the console.

(2026-08-19)

1.418.2

Patch Changes

#4555 3e0edff Thanks @HaynesPostHog! - Fix a Chrome renderer crash (grey "Aw, Snap" tab, "Error code: 5") that could still occur when closing an in-app survey on a heavy page such as a large dashboard.

Closing a survey animated the fade-out with document.startViewTransition, which snapshots the entire page viewport. The survey applied no view-transition-name scoping, so on a heavy host page capturing that whole-page snapshot could exhaust renderer memory and crash the tab. A previous fix addressed a related crash (a snapshot pointing at a removed node) but left the document-level transition — and its whole-page snapshot cost — in place.

The survey renders in an isolated shadow root, so it never needed a document-level transition. The close now fades the popup out with a plain CSS opacity transition scoped to the survey's own container, then unmounts it once the fade has run. No whole-page snapshot, no crash, same fade-out UX. (2026-08-19)

1.5.0

Minor Changes

• #4541 74d8f5a Thanks @ablaszkiewicz! - Add experimental sourcemaps.releaseMode: 'event' to the rollup plugin. In event mode the plugin resolves the release with posthog-cli release resolve and injects its id into every chunk, so exceptions report their release directly instead of it being bound to the uploaded symbol sets, and chunk ids are derived from chunk content so a rebuild of unchanged code reuses the symbol set already uploaded. The option defaults to the POSTHOG_RELEASE_MODE environment variable and then to symbol-set, which behaves exactly as before. Event mode needs a posthog-cli with the release resolve command.
• (2026-08-19)

Patch Changes

• #4541 74d8f5a Thanks @ablaszkiewicz! - Bump @posthog/cli to ~0.13.0, which ships the release resolve command the rollup plugin's event release mode spawns.
• (2026-08-19)

Updated dependencies [74d8f5a]

• @posthog/[email protected]

1.2.0

Minor Changes

#4541 74d8f5a Thanks @ablaszkiewicz! - Add experimental sourcemaps.releaseMode: 'event' to the rollup plugin. In event mode the plugin resolves the release with posthog-cli release resolve and injects its id into every chunk, so exceptions report their release directly instead of it being bound to the uploaded symbol sets, and chunk ids are derived from chunk content so a rebuild of unchanged code reuses the symbol set already uploaded. The option defaults to the POSTHOG_RELEASE_MODE environment variable and then to symbol-set, which behaves exactly as before. Event mode needs a posthog-cli with the release resolve command.

(2026-08-19)