chore(deps): update dependency posthog-node to v5.45.2

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
posthog-node (source)	5.11.2 → 5.45.2

---

Release Notes

PostHog/posthog-js (posthog-node)

v5.45.2

Compare Source

Patch Changes

• #​4168 06d19a2 Thanks @​dustinbyrne! - Avoid Next.js Edge runtime warnings for native compression and fatal error handling.
  (2026-07-16)
• Updated dependencies [06d19a2]:
  • @​posthog/core@​1.43.1

v5.45.1

Compare Source

Patch Changes

• #​4164 9eb2b28 Thanks @​dustinbyrne! - Fix the default Node.js event flush interval at 5 seconds.
  (2026-07-16)

v5.45.0

Compare Source

Minor Changes

• #​4159 fad6d9a Thanks @​haacked! - add $feature_flag_has_experiment to $feature_flag_called events

  $feature_flag_called events now carry a $feature_flag_has_experiment boolean sourced from the server's has_experiment flag metadata (the /flags?v=2 response for remote evaluation, the /api/feature_flag/local_evaluation definitions for posthog-node local evaluation). The property is only sent when the server explicitly reports has_experiment; it is omitted entirely when the value is unknown (older servers, missing metadata, bootstrapped or locally injected flags). (2026-07-16)

Patch Changes

• Updated dependencies [fad6d9a]:
  • @​posthog/core@​1.43.0

v5.44.0

Compare Source

Minor Changes

• #​4153 fc2cb2e Thanks @​eli-r-ph! - Raise the default maxQueueSize from 1000 to 10000. Backend workloads are more likely to burst-enqueue events synchronously ahead of a flush than browser/mobile clients, so the previous default risked silently dropping events under bursty load. An explicit maxQueueSize option still overrides this default.
  (2026-07-15)

Patch Changes

• Updated dependencies [fc2cb2e]:
  • @​posthog/core@​1.42.1

v5.43.0

Compare Source

Minor Changes

• #​4117 1eddff7 Thanks @​DanielVisca! - add the posthog.metrics API (count, gauge, histogram) to posthog-node — alpha

  Backend services can now record metrics through the same statsd-style pre-aggregating client the browser SDK ships, with no OpenTelemetry setup:

  const client = new PostHog('phc_...', { metrics: { serviceName: 'billing-worker' } })
  client.metrics.count('invoices.processed', 1, { attributes: { plan: 'pro' } })
  client.metrics.gauge('queue.depth', 42)
  client.metrics.histogram('job.duration', 187, { unit: 'ms' })

  Samples aggregate in memory and flush as OTLP/JSON to /i/v1/metrics (one data point per series per window). Pending metrics are flushed on shutdown(). Core gains _sendMetricsBatch on PostHogCoreStateless (same outcome contract as _sendLogsBatch) and a shared resolveMetricsConfig, so any core-based SDK can host PostHogMetrics. (2026-07-15)

Patch Changes

• Updated dependencies [1eddff7]:
  • @​posthog/core@​1.42.0

v5.42.0

Compare Source

Minor Changes

• #​4101 dc2aa5b Thanks @​posthog! - Expose the error tracking rate-limiter config via the new exceptionRateLimiterRefillRate and exceptionRateLimiterBucketSize options. Burst protection is scoped per exception type (each distinct $exception type gets its own token bucket, with no aggregate cap across types), so these let customers with high-cardinality exception types tune the per-type allowance.
  (2026-07-14)

Patch Changes

• Updated dependencies [dc2aa5b]:
  • @​posthog/core@​1.41.0

v5.41.0

Compare Source

Minor Changes

• #​4105 203284a Thanks @​eli-r-ph! - Add opt-in Capture V1 support. Set the POSTHOG_CAPTURE_MODE=v1 environment variable to submit analytics events to the Capture V1 endpoint (/i/v1/analytics/events) instead of the legacy /batch/ endpoint, on both the batched and immediate send paths. The default remains v0, so existing behavior is unchanged unless you opt in. Opt-in is env-var-only during the transition (no public option), so nothing on the API surface has to be removed when v1 later becomes the default.

  Capture V1 uses Bearer auth, lifts legacy $-sentinel properties into a typed options object, and does per-event partial retry with exponential backoff clamped against Retry-After. Dropped and undelivered events are surfaced on the client error channel as a CaptureV1Error. $ai_* events continue to use the legacy submitter for now, regardless of the capture mode.

  In v1 mode, $ai_* events are routed to an isolated in-memory queue and flushed independently of the Capture V1 queue, so the two transports never share a batch and a failure on one cannot re-send events already accepted on the other. Each queue keeps its own retry/durability semantics: the legacy queue re-queues on network failure (retrying on later flushes), while the V1 queue exhausts the sender's own attempt budget per cycle and then surfaces the failure rather than re-queuing. (2026-07-11)

Patch Changes

• Updated dependencies [203284a]:
  • @​posthog/core@​1.40.2

v5.40.0

Compare Source

Minor Changes

• #​4060 0b49a4c Thanks @​turnipdabeets! - Add secretKey config as the canonical alias for the deprecated personalApiKey (accepts a Personal API Key or Project Secret API Key).
  (2026-07-07)

v5.39.4

Compare Source

Patch Changes

• #​4047 0c11747 Thanks @​marandaneto! - Stop duplicating distinct_id inside /flags person properties.
  (2026-07-02)
• Updated dependencies [5e7e132]:
  • @​posthog/core@​1.39.5

v5.39.3

Compare Source

Patch Changes

• #​4055 64e04ba Thanks @​marandaneto! - Retry /flags requests that receive HTTP 502 or 504 responses across SDKs that use the shared core flags client.
  (2026-07-02)
• Updated dependencies [64e04ba]:
  • @​posthog/core@​1.39.4

v5.39.2

Compare Source

Patch Changes

• #​4028 a664b81 Thanks @​marandaneto! - Make Node flush() wait for pending asynchronous SDK work before draining the event queue, so events produced by helpers like captureException() are not missed. Pending work rejections no longer prevent queued events from flushing.
  (2026-07-01)
• Updated dependencies [a664b81]:
  • @​posthog/core@​1.39.3

v5.39.1

Compare Source

Patch Changes

• #​4029 b36b1cc Thanks @​marandaneto! - Call before_send for identify, group identify, and alias events.
  (2026-06-30)

• #​4027 ab118d2 Thanks @​marandaneto! - Safely serialize event batches with circular property references instead of crashing during flush.
  (2026-06-30)

• Updated dependencies [ab118d2]:

  • @​posthog/core@​1.39.2

v5.39.0

Compare Source

Minor Changes

• #​4006 0063128 Thanks @​github-actions! - Add groupIdentifyImmediate() to await the network request when identifying a group, mirroring captureImmediate/identifyImmediate/aliasImmediate. Useful in edge/serverless environments where the background queue may not flush. The Convex integration now uses it directly instead of routing $groupidentify through captureImmediate.
  (2026-06-30)

Patch Changes

• Updated dependencies [0063128]:
  • @​posthog/core@​1.39.0

v5.38.8

Compare Source

Patch Changes

• #​3974 08b404b Thanks @​mjfaga! - Fix local evaluation ignoring the in/not_in operator on cohort-based flag conditions. "Not in
  cohort" was evaluated as "in cohort", inverting cohort-exclusion flags. Now applies the operator to
  the cohort membership result. (2026-06-29)

v5.38.7

Compare Source

Patch Changes

• #​3961 619a25c Thanks @​marandaneto! - Retry feature flag requests after transient network errors only. The feature flag request retry count defaults to 1 and can be set to 0 to disable retries.
  (2026-06-29)
• Updated dependencies [619a25c]:
  • @​posthog/core@​1.38.1

v5.38.6

Compare Source

Patch Changes

• #​3896 606ef43 Thanks @​GauthierPLM! - Only stamp $groups from the top-level groups when present
  (2026-06-26)

v5.38.5

Compare Source

Patch Changes

• #​3955 8e9689a Thanks @​marandaneto! - Dedupe feature flag called events per returned flag value.
  (2026-06-24)
• Updated dependencies [8e9689a]:
  • @​posthog/core@​1.37.3

v5.38.4

Compare Source

Patch Changes

• #​3938 6391106 Thanks @​dustinbyrne! - Respect disable_capture_url_hashes when capturing Express and NestJS request URLs.
  (2026-06-23)

v5.38.3

Compare Source

Patch Changes

• #​3937 4d59d0e Thanks @​marandaneto! - Deprecate the Node SDK Sentry integration and point users to PostHog Error Tracking for Node.
  (2026-06-23)
• Updated dependencies [440e370]:
  • @​posthog/core@​1.37.0

v5.38.2

Compare Source

Patch Changes

• #​3903 6b21f77 Thanks @​marandaneto! - Validate custom event UUID overrides and generate new UUIDs when invalid.
  (2026-06-19)
• Updated dependencies [6b21f77]:
  • @​posthog/core@​1.35.3

v5.38.1

Compare Source

Patch Changes

• #​3886 e6d7fe2 Thanks @​marandaneto! - Stop sending deprecated no-op top-level type, library, and library_version fields in event batch payloads. Use properties.$lib and properties.$lib_version for SDK metadata; legacy queued library and library_version values are used as fallbacks when the official $ properties are missing.
  (2026-06-18)
• Updated dependencies [e6d7fe2]:
  • @​posthog/core@​1.35.2

v5.38.0

Compare Source

Minor Changes

• #​3845 a0553b3 Thanks @​marandaneto! - Add setPersonProperties() and unsetPersonProperties() helpers to manage person properties from the Node.js SDK.
  (2026-06-16)

Patch Changes

• Updated dependencies [b3ec845, c6c163a]:
  • @​posthog/core@​1.33.0

v5.37.1

Compare Source

Patch Changes

• #​3837 29bf8e3 Thanks @​marandaneto! - Add missing bugs metadata to package manifests.
  (2026-06-15)
• Updated dependencies [29bf8e3]:
  • @​posthog/core@​1.32.4

v5.37.0

Compare Source

Minor Changes

• #​3705 d6fc0a5 Thanks @​gustavohstrassburger! - feat(feature-flags): support the early_exit condition option in local evaluation. When a flag enables early exit, evaluation now stops and returns false as soon as a condition group's property filters match but the rollout percentage excludes the user, instead of falling through to later groups — matching the server-side evaluation behavior.
  (2026-06-12)

v5.36.17

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.32.3

v5.36.16

Compare Source

Patch Changes

• Updated dependencies [25822ac]:
  • @​posthog/core@​1.32.2

v5.36.15

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.32.1

v5.36.14

Compare Source

Patch Changes

• Updated dependencies [612f97a]:
  • @​posthog/core@​1.32.0

v5.36.13

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.31.4

v5.36.12

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.31.3

v5.36.11

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.31.2

v5.36.10

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.31.1

v5.36.9

Compare Source

Patch Changes

• Updated dependencies [0c2acb9]:
  • @​posthog/core@​1.31.0

v5.36.8

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.14

v5.36.7

Compare Source

Patch Changes

• #​3748 7820929 Thanks @​marandaneto! - Reduce duplicate internal code found by dry4ts.
  (2026-06-09)
• Updated dependencies []:
  • @​posthog/core@​1.30.13

v5.36.6

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.12

v5.36.5

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.11

v5.36.4

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.10

v5.36.3

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.9

v5.36.2

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.8

v5.36.1

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.7

v5.36.0

Compare Source

Minor Changes

• #​3728 9287c87 Thanks @​turnipdabeets! - Add a configurable $is_server event property (default true) so PostHog can identify server-side events. Set isServer: false when using the SDK as a client/CLI so the device OS is attributed normally.
  (2026-06-04)

v5.35.15

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.6

v5.35.14

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.5

v5.35.13

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.4

v5.35.12

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.3

v5.35.11

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.2

v5.35.10

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.30.1

v5.35.9

Compare Source

Patch Changes

• #​3703 f3cc6fa Thanks @​marandaneto! - Disable/no-op initialization paths instead of throwing or sending requests when PostHog project tokens are missing or blank.
  (2026-06-01)
• Updated dependencies [3d4a76f]:
  • @​posthog/core@​1.30.0

v5.35.8

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.15

v5.35.7

Compare Source

Patch Changes

• Updated dependencies [d9ad199]:
  • @​posthog/core@​1.29.14

v5.35.6

Compare Source

Patch Changes

• #​3681 7b84b75 Thanks @​ablaszkiewicz! - unify captureException in posthog core
  (2026-05-28)
• Updated dependencies [7b84b75]:
  • @​posthog/core@​1.29.13

v5.35.5

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.12

v5.35.4

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.11

v5.35.3

Compare Source

Patch Changes

• Updated dependencies [5568f12]:
  • @​posthog/core@​1.29.10

v5.35.2

Compare Source

Patch Changes

• #​3658 5d7a2d3 Thanks @​gustavohstrassburger! - Include group context in the $feature_flag_called deduplication key in _captureFlagCalledEventIfNeeded, so events fire independently per group combination.
  (2026-05-25)

v5.35.1

Compare Source

Patch Changes

• Updated dependencies [c806cca]:
  • @​posthog/core@​1.29.9

v5.35.0

Compare Source

Minor Changes

• #​3642 18ea8b5 Thanks @​dustinbyrne! - Promote feature flag definition cache provider types to the main posthog-node export and deprecate posthog-node/experimental imports.
  (2026-05-21)

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.8

v5.34.10

Compare Source

Patch Changes

• #​3643 f42f371 Thanks @​dmarticus! - Reject semver values with leading zeros in local flag evaluation. Per semver 2.0.0 §2, numeric identifiers must not include leading zeros — values like 1.07.3 are not valid semver and should not match targeting conditions. Both override values and flag values are now validated; invalid inputs surface as InconclusiveMatchError so the condition does not match.
  (2026-05-21)

v5.34.9

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.7

v5.34.8

Compare Source

Patch Changes

• #​3640 12ef3f6 Thanks @​hpouillot! - Fix identifyImmediate to await the underlying network request. Previously the returned promise resolved before the $identify event was sent, causing events to be dropped when called from short-lived runtimes (Vercel/Cloudflare Workers, Convex actions) that exit immediately after await.
  (2026-05-21)

v5.34.7

Compare Source

Patch Changes

• Updated dependencies [a880dbc]:
  • @​posthog/core@​1.29.6

v5.34.6

Compare Source

Patch Changes

• #​3623 e119eec Thanks @​richardsolomou! - Fix six edge cases in local feature flag evaluation. gt/gte/lt/lte now compare numerically when both sides parse as finite numbers — previously a string override like "10" against numeric value 9 slipped into lexicographic comparison and returned false, and parseFloat's NaN return value leaked through the old != null guard. is_not_set now resolves locally — true when the property key is absent, false when present — instead of always throwing InconclusiveMatchError and forcing the flag to return undefined. Flag-level condition properties with negation: true are now correctly inverted, matching the existing cohort-path behavior in matchPropertyGroup. An inactive flag (active: false) now short-circuits to false even when ensure_experience_continuity: true — previously it threw InconclusiveMatchError and resolved to undefined. is_set now returns true for properties whose value is null or undefined as long as the key is present — is_set is about key presence, not value. Cohort property groups containing a flag-type property no longer silently skip the dependency; the cohort eval is now marked inconclusive so the flag returns undefined instead of a wrong definitive answer.
  (2026-05-19)

v5.34.5

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.5

v5.34.4

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.4

v5.34.3

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.3

v5.34.2

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.29.2

v5.34.1

Compare Source

Patch Changes

• Updated dependencies [4b895bf]:
  • @​posthog/core@​1.29.1

v5.34.0

Compare Source

Minor Changes

• #​3599 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

• Updated dependencies [ad60818]:
  • @​posthog/core@​1.29.0

v5.33.7

Compare Source

Patch Changes

• Updated dependencies [223d925]:
  • @​posthog/core@​1.28.7

v5.33.6

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.28.6

v5.33.5

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.28.5

v5.33.4

Compare Source

Patch Changes

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

v5.33.3

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.28.3

v5.33.2

Compare Source

Patch Changes

• #​3516 220cd61 Thanks @​marandaneto! - fix: consume fetch response body to prevent CF Workers runtime warnings
  (2026-05-04)
• Updated dependencies [220cd61, 255b273]:
  • @​posthog/core@​1.28.2

v5.33.1

Compare Source

Patch Changes

• Updated dependencies [8aee3d5]:
  • @​posthog/core@​1.28.1

v5.33.0

Compare Source

Minor Changes

• #​3476 f8bc02f Thanks @​dmarticus! - Add evaluateFlags() and a new flags option on capture() so a single /flags request powers both flag branching and event enrichment per incoming request:

  const flags = await posthog.evaluateFlags(distinctId, { personProperties: { plan: 'enterprise' } })
  if (flags.isEnabled('new-dashboard')) {
    renderNewDashboard()
  }
  posthog.capture({ distinctId, event: 'page_viewed', flags })

  The returned FeatureFlagEvaluations snapshot exposes isEnabled(), getFlag(), getFlagPayload() for branching, plus onlyAccessed() and only([keys]) for filtering which flags get attached to a captured event. Pass flagKeys: [...] to evaluateFlags() to scope the underlying /flags request itself. captureException() / captureExceptionImmediate() accept a flags argument so $exception events carry the same flag context as the rest of your request's events.

  Deprecates isFeatureEnabled(), getFeatureFlag(), getFeatureFlagPayload(), and capture({ sendFeatureFlags }). They continue to work but now log a deduped [PostHog] ... is deprecated warning the first time they're used. Removal is planned for the next major version. (2026-05-02)

v5.32.1

Compare Source

Patch Changes

• Updated dependencies [cf56753, 04db756]:
  • @​posthog/core@​1.28.0

v5.32.0

Compare Source

Minor Changes

• #​3474 70ba8f8 Thanks @​patricio-posthog! - feat(flags): support mixed targeting in local evaluation
  (2026-04-30)

v5.31.0

Compare Source

Minor Changes

• #​3491 974e4b2 Thanks @​dustinbyrne! - Add Express and NestJS request context support for PostHog tracing headers.
  (2026-04-29)

v5.30.8

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.27.9

v5.30.7

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.27.8

v5.30.6

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.27.7

v5.30.5

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.27.6

v5.30.4

Compare Source

Patch Changes

• Updated dependencies [70508df]:
  • @​posthog/core@​1.27.5

v5.30.3

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.27.4

v5.30.2

Compare Source

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.27.3

v5.30.1

Compare Source

Patch Changes

• Updated dependencies [daf028d]:
  • @​posthog/core@​1.27.2

v5.30.0

Compare Source

Minor Changes

• #​3457 eadbcd7 Thanks @​hpouillot! - send relative file paths in frames
  (2026-04-23)

v5.29.7

Compare Source

Patch Changes

• Updated dependencies [96f19b7]:
  • @​posthog/core@​1.27.1

[v5.29.6](https://redirect.github.com/Po

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • "before 4am"

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.