chore(deps): bump posthog-node from 5.36.3 to 5.41.0

[dependabot]

Bumps posthog-node from 5.36.3 to 5.41.0.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.41.0

5.41.0

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

posthog-node@5.40.0

5.40.0

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)

posthog-node@5.39.4

5.39.4

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

posthog-node@5.39.3

5.39.3

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

posthog-node@5.39.2

5.39.2

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.

... (truncated)

Changelog

Sourced from posthog-node's changelog.

5.41.0

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

5.40.0

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)

5.39.4

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

5.39.3

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

5.39.2

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

5.39.1

... (truncated)

Commits

• d7f7c8e chore: update versions and lockfile [version bump]
• 203284a refactor(core): extract sendBatch seam for capture pluggability (#4105)
• d0e531a fix(core): coalesce concurrent flushes (#4120)
• 954919d chore: update versions and lockfile [version bump]
• 0b49a4c feat(node): add secretKey config, deprecate personalApiKey (#4060)
• 859fd44 chore(deps): weekly safe npm updates · 10 packages (#4087)
• 0ba87cb chore: update versions and lockfile [version bump]
• 0c11747 fix: stop duplicating distinct_id in flags person properties (#4047)
• 4eb8b21 chore: update versions and lockfile [version bump]
• dd90e55 test(node): make local polling tests deterministic (#4043)
• Additional commits viewable in compare view