PostHog

4.45.0

Minor Changes

• #3552 387ca37 Thanks @ioannisj! - Add support for the experimental iOS session replay option sessionReplayConfig.screenshotModeBackgroundCapture (2026-05-09)

Build from cf8efad5764d4a78f815919c2943d6abbb779e98

Build from 20e91e3a13c765e3aaa9636f677b1eca93f634cf

Build from ca925b1dbd520c6ef030363b0e9092852556b4d6

4.44.4

Patch Changes

• Updated dependencies []:
  • @posthog/types@1.372.10
  • @posthog/core@1.28.4

1.372.10

5.33.4

Patch Changes

• Updated dependencies []:
  • @posthog/core@1.28.4

1.372.10

Patch Changes

• #3544 d120042 Thanks @ksvat! - fix: stop session recording before destroying sessionManager in opt_out_capturing() with cookieless_mode: "on_reject". Previously, queued/throttled rrweb events (e.g. mousemove) could fire after the sessionManager was set to undefined and throw [SessionRecording] must be started with a valid sessionManager. Also adds a defensive early-return in onRRwebEmit so any remaining late events bail out instead of throwing. (2026-05-07)

• #3542 94a5ba0 Thanks @TueHaulund! - Preserve <style> textContent when the browser's CSSOM serialization would emit empty longhands from var() inside a shorthand. When a stylesheet has e.g. padding: var(--p); padding-bottom: var(--pb);, browsers store the shorthand's longhands with empty token lists per the CSS Custom Properties spec, and CSSStyleRule.cssText re-emits them as padding-top: ; padding-right: ; padding-left: ;. The previous behavior replaced the <style> text with that corrupted output, silently dropping layout rules on replay. We now detect the empty-longhand pattern and keep the original textContent in that case. Affects users of any CSS-in-JS framework that combines var() with shorthands (Chakra UI v3, Panda CSS, Emotion, etc.). Same class of bug as rrweb-io/rrweb#1667. (2026-05-07)

• Updated dependencies []:

  • @posthog/types@1.372.10
  • @posthog/core@1.28.4

1.7.25

Patch Changes

• Updated dependencies [d120042, 94a5ba0]:
  • posthog-js@1.372.10
  • @posthog/core@1.28.4
  • posthog-node@5.33.4

1.4.20

Patch Changes

• Updated dependencies []:
  • @posthog/core@1.28.4

7.18.1

Patch Changes

• Updated dependencies []:
  • @posthog/core@1.28.4
  • posthog-node@5.33.4

4.6.19

Patch Changes

• Updated dependencies []:
  • @posthog/core@1.28.4

1.9.20

Patch Changes

• Updated dependencies []:
  • @posthog/webpack-plugin@1.4.20

0.4.44

Patch Changes

• Updated dependencies [d120042, 94a5ba0]:
  • posthog-js@1.372.10
  • @posthog/core@1.28.4
  • posthog-node@5.33.4

0.2.24

Patch Changes

• Updated dependencies []:
  • @posthog/core@1.28.4
  • posthog-node@5.33.4

1.28.4

Patch Changes

• Updated dependencies []:
  • @posthog/types@1.372.10

0.4.43

Patch Changes

• #3543 ece3097 Thanks @dustinbyrne! - Publish @posthog/next from the release workflow so npm catches up with the versions already recorded in the changelog. (2026-05-07)

7.18.0

Minor Changes

• #3539 6b23fd3 Thanks @carlos-marchal-ph! - Added a new generic binary payload sanitizer to catch more edge cases (2026-05-07)

Build from bcd36ec230ef3aefaab9616914faee40e90467ef

Build from 4af7eef0621fa6d7b742a01ec86e28925e12309a