[dependabot]

Bumps posthog-node from 5.57.2 to 5.60.1.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.60.1

5.60.1

Patch Changes

• #5471 0058ef9 Thanks @​gustavohstrassburger! - fix: let later conditions resolve a flag locally when an unexpected error follows a filter that local evaluation cannot check, instead of failing the whole flag (2026-10-29)

• #5471 0058ef9 Thanks @​gustavohstrassburger! - fix: fall back to the server when a flag depends on a flag that only the server can evaluate (for example, one with a static cohort), instead of letting a later condition choose a different value locally. unresolvedFlags reports such a flag as unresolved_dependency (2026-10-29)

posthog-node@5.60.0

5.60.0

Minor Changes

• #5270 4b25f7f Thanks @​DanielVisca! - The Express and NestJS integrations can read the session ID, and the distinct ID of an identified user, from the posthog-js cookie when a request has no tracing headers, so backend events link to browser sessions on same-site requests without frontend configuration. Turn it on with the readPostHogCookie option. (2026-10-29)

posthog-node@5.59.0

5.59.0

Minor Changes

• #5252 503c3ea Thanks @​andehen! - Reads from an evaluateFlags() snapshot now honor sendFeatureFlagEvent: false, and isEnabled() / getFlag() accept a sendFeatureFlagEvents option that overrides it for one read. If you set sendFeatureFlagEvent: false and rely on snapshot reads for experiment exposures, pass sendFeatureFlagEvents: true on those reads. (2026-10-28)

Patch Changes

• Updated dependencies [503c3ea]:
  • @​posthog/core@​1.61.2

posthog-node@5.58.0

5.58.0

Minor Changes

• #5314 096131d Thanks @​pauldambra! - Add an optional OpenTelemetry context processor, and an optional signal that ends a context's lifetime. (2026-10-28)

Changelog

Sourced from posthog-node's changelog.

5.60.1

Patch Changes

• #5471 0058ef9 Thanks @​gustavohstrassburger! - fix: let later conditions resolve a flag locally when an unexpected error follows a filter that local evaluation cannot check, instead of failing the whole flag (2026-10-29)

• #5471 0058ef9 Thanks @​gustavohstrassburger! - fix: fall back to the server when a flag depends on a flag that only the server can evaluate (for example, one with a static cohort), instead of letting a later condition choose a different value locally. unresolvedFlags reports such a flag as unresolved_dependency (2026-10-29)

5.60.0

Minor Changes

• #5270 4b25f7f Thanks @​DanielVisca! - The Express and NestJS integrations can read the session ID, and the distinct ID of an identified user, from the posthog-js cookie when a request has no tracing headers, so backend events link to browser sessions on same-site requests without frontend configuration. Turn it on with the readPostHogCookie option. (2026-10-29)

5.59.0

Minor Changes

• #5252 503c3ea Thanks @​andehen! - Reads from an evaluateFlags() snapshot now honor sendFeatureFlagEvent: false, and isEnabled() / getFlag() accept a sendFeatureFlagEvents option that overrides it for one read. If you set sendFeatureFlagEvent: false and rely on snapshot reads for experiment exposures, pass sendFeatureFlagEvents: true on those reads. (2026-10-28)

Patch Changes

• Updated dependencies [503c3ea]:
  • @​posthog/core@​1.61.2

5.58.0

Minor Changes

• #5314 096131d Thanks @​pauldambra! - Add an optional OpenTelemetry context processor, and an optional signal that ends a context's lifetime. (2026-10-28)

Commits

• 4949cec chore: update versions and lockfile [version bump]
• 0058ef9 fix(node): keep local flag evaluation consistent with the server (#5471)
• 73d787a chore: update versions and lockfile [version bump]
• 4b25f7f feat(node): opt-in posthog-js cookie fallback for request context (#5270)
• 6f11d8e chore: update versions and lockfile [version bump]
• 503c3ea feat(node): honor sendFeatureFlagEvent in evaluateFlags snapshots, with a per...
• 4044a5c chore: update versions and lockfile [version bump]
• 096131d feat(node): add request context to OpenTelemetry spans (#5314)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: pierreb-devkit/Node
• Branch: master
• File: .coderabbit.yaml
• Commit: f902e86
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 12de6599-0aff-40de-b0c4-15a2eed33d47

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn