[dependabot]

Bumps posthog-node from 5.61.0 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)

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)

Commits

• 2178de7 chore: update versions and lockfile [version bump]
• de8435f fix(node): capture unhandled rejections when the host has its own listener (#...
• 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: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: f9c1b071-267c-4a84-9132-70658bbb2bc5

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

[github-actions]

Thanks @dependabot[bot] for keeping our dependencies current! 🙌

[github-actions]

Automated approval for Dependabot dependency update.

[hermes-exosphere]

Automated approval: trivial dependency update.

Checked posthog-node 5.61.0 → 5.61.1 against upstream release notes, published tarballs and repository usage. The changed exception-autocapture behavior is not enabled here, and the isolated lockfile update satisfies the existing manifest range. No new compatibility or supply-chain concerns require human review.

Bumps

• posthog-node 5.61.0 → 5.61.1 (Patch)

Findings

• info posthog-node: Release notes and published code show exception-autocapture fixes. Autocapture remains disabled by default; lib/telemetry.ts does not enable it, and the repository does not call captureException.
• info posthog-node: Only the version and integrity hash change. Both tarball hashes verify against npm and the lockfile; dependencies, exports, runtime requirements and scripts are unchanged. No install lifecycle scripts, native builds, binary downloads, new transitive packages or Actions changes.
• info posthog-node: The existing license discrepancy—MIT metadata versus an Apache-2.0 bundled LICENSE—is identical in both versions; this patch changes neither.

Checked: allowlisted bot author, only dependency files, patch/minor bumps, green CI on this commit, no merge conflicts; then a supply-chain review by gpt-6.1-sol (changelogs, install scripts, lockfile, action pins).

_{pr-autopilot · Codex in a locked-down container · traced by failproofai}