[dependabot]

Bumps posthog-node from 5.55.3 to 5.61.1.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.61.1

5.61.1

Patch Changes

• #5472 de8435f Thanks @​ablaszkiewicz! - fix: exception autocapture now captures unhandled promise rejections when the app or framework (for example Next.js, Nitro or PM2) has its own unhandledRejection listener, without changing what Node does with the rejection. Each occurrence is captured once per project, however many clients the app creates, and an error reported more than once in the same turn of the event loop (rethrown by a host listener, or one Error object rejected by two promises) is captured once. When the process survives the error, autocapture captures it at the end of the current turn of the event loop, so that a captureException call for the same error in that turn, from the app's own listener or a framework's error hook such as Nitro's, is the one sent, with its distinctId and properties. A captureException call for an error that autocapture already captured in the same turn is skipped. When the app flushes or shuts down a client, that client captures at once what is still waiting for the end of the turn, so a crash handler that flushes or shuts down and then exits still sends the error. A crash is captured whatever the error, an AbortError or a framework's control flow included. A rejection that the app handles only later is still captured, as Node reports it as unhandled. Next.js and React control-flow errors and AbortError rejections are skipped when the process survives them. (2026-10-30)

posthog-node@5.61.0

5.61.0

Minor Changes

• #5418 c705824 Thanks @​mayteio! - Send transactional email from a PostHog email template with posthog.emails.send(), using the new appHost, emailRequestTimeoutMs and emailRequestMaxRetries client options. Read what happened to a sent email with posthog.emails.get(id), using the message ID that send() returned. (2026-10-30)

Patch Changes

• Updated dependencies [c705824]:
  • @​posthog/core@​1.62.0

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

... (truncated)

Changelog

Sourced from posthog-node's changelog.

5.61.1

Patch Changes

• #5472 de8435f Thanks @​ablaszkiewicz! - fix: exception autocapture now captures unhandled promise rejections when the app or framework (for example Next.js, Nitro or PM2) has its own unhandledRejection listener, without changing what Node does with the rejection. Each occurrence is captured once per project, however many clients the app creates, and an error reported more than once in the same turn of the event loop (rethrown by a host listener, or one Error object rejected by two promises) is captured once. When the process survives the error, autocapture captures it at the end of the current turn of the event loop, so that a captureException call for the same error in that turn, from the app's own listener or a framework's error hook such as Nitro's, is the one sent, with its distinctId and properties. A captureException call for an error that autocapture already captured in the same turn is skipped. When the app flushes or shuts down a client, that client captures at once what is still waiting for the end of the turn, so a crash handler that flushes or shuts down and then exits still sends the error. A crash is captured whatever the error, an AbortError or a framework's control flow included. A rejection that the app handles only later is still captured, as Node reports it as unhandled. Next.js and React control-flow errors and AbortError rejections are skipped when the process survives them. (2026-10-30)

5.61.0

Minor Changes

• #5418 c705824 Thanks @​mayteio! - Send transactional email from a PostHog email template with posthog.emails.send(), using the new appHost, emailRequestTimeoutMs and emailRequestMaxRetries client options. Read what happened to a sent email with posthog.emails.get(id), using the message ID that send() returned. (2026-10-30)

Patch Changes

• Updated dependencies [c705824]:
  • @​posthog/core@​1.62.0

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

... (truncated)

Commits

• 2178de7 chore: update versions and lockfile [version bump]
• de8435f fix(node): capture unhandled rejections when the host has its own listener (#...
• decaa16 chore: update versions and lockfile [version bump]
• c705824 feat(node): send transactional email from a template (#5418)
• 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...
• Additional commits viewable 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)

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/openworkflowdev/openworkflow/@openworkflow/cli@954

npm i https://pkg.pr.new/openworkflowdev/openworkflow/@openworkflow/dashboard@954

npm i https://pkg.pr.new/openworkflowdev/openworkflow@954

commit: 1ad9a6a