Skip to content

build(deps): bump posthog-node from 5.64.0 to 5.71.0 - #4287

Merged
github-actions[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/posthog-node-5.71.0
Nov 16, 2026
Merged

github-actions[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/posthog-node-5.71.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Bumps posthog-node from 5.64.0 to 5.71.0.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.71.0

5.71.0

Minor Changes

  • #5630 2877954 Thanks @​Silthus! - A send with templateKey now takes tracking and sensitive.

    tracking chooses what PostHog tracks for the email. tracking: true turns on opens, clicks and engagement events. tracking: false turns them all off. An object such as { clicks: true } or { engagement: false } turns each kind on or off, and a key you leave out keeps its default. Without it, PostHog counts opens, captures engagement events, and counts clicks only when the email isn't sensitive.

    sensitive marks an email that carries login links, reset tokens or codes. A sensitive email keeps its links as they are unless tracking turns clicks on, leaves its subject off engagement events, and keeps its content out of PostHog's logs. Without it, a send whose templateKey matches a template saved in PostHog follows that template's setting, and any other send is sensitive. PostHog refuses sensitive: false when the matching template is sensitive. A send that sets neither option works exactly as before.

    captureEngagement is deprecated in favor of tracking: { engagement: false }. It keeps working, but PostHog refuses a send that sets both.

    tracking and sensitive need PostHog's API support, which is rolling out. Until it reaches your PostHog instance, PostHog refuses a send that sets either one. (2026-11-12)

posthog-node@5.70.0

5.70.0

Minor Changes

  • #5511 b64482a Thanks @​Silthus! - Opt a recipient out of email topics, or back in, with posthog.emails.setPreferences({ to, topics, allMarketing }). One call sends the whole change in one request, using the client's secretKey. (2026-11-12)

posthog-node@5.69.0

5.69.0

Minor Changes

  • #5634 ccd042a Thanks @​Silthus! - posthog.emails.send() takes a React Email element as react and renders it with the optional peer @react-email/render. (2026-11-11)

posthog-node@5.68.2

5.68.2

Patch Changes

  • #5637 5fc2aab Thanks @​andehen! - With POSTHOG_CAPTURE_MODE=v1, capture now retries 404 and 429 responses like 408 and 5xx instead of failing the batch at once. (2026-11-10)

posthog-node@5.68.1

5.68.1

Patch Changes

  • #5649 69b3cb8 Thanks @​marandaneto! - Fix empty OR and legacy cohort group matching, and fall back to the server for unsupported group types. (2026-11-10)

posthog-node@5.68.0

5.68.0

... (truncated)

Changelog

Sourced from posthog-node's changelog.

5.71.0

Minor Changes

  • #5630 2877954 Thanks @​Silthus! - A send with templateKey now takes tracking and sensitive.

    tracking chooses what PostHog tracks for the email. tracking: true turns on opens, clicks and engagement events. tracking: false turns them all off. An object such as { clicks: true } or { engagement: false } turns each kind on or off, and a key you leave out keeps its default. Without it, PostHog counts opens, captures engagement events, and counts clicks only when the email isn't sensitive.

    sensitive marks an email that carries login links, reset tokens or codes. A sensitive email keeps its links as they are unless tracking turns clicks on, leaves its subject off engagement events, and keeps its content out of PostHog's logs. Without it, a send whose templateKey matches a template saved in PostHog follows that template's setting, and any other send is sensitive. PostHog refuses sensitive: false when the matching template is sensitive. A send that sets neither option works exactly as before.

    captureEngagement is deprecated in favor of tracking: { engagement: false }. It keeps working, but PostHog refuses a send that sets both.

    tracking and sensitive need PostHog's API support, which is rolling out. Until it reaches your PostHog instance, PostHog refuses a send that sets either one. (2026-11-12)

5.70.0

Minor Changes

  • #5511 b64482a Thanks @​Silthus! - Opt a recipient out of email topics, or back in, with posthog.emails.setPreferences({ to, topics, allMarketing }). One call sends the whole change in one request, using the client's secretKey. (2026-11-12)

5.69.0

Minor Changes

  • #5634 ccd042a Thanks @​Silthus! - posthog.emails.send() takes a React Email element as react and renders it with the optional peer @react-email/render. (2026-11-11)

5.68.2

Patch Changes

  • #5637 5fc2aab Thanks @​andehen! - With POSTHOG_CAPTURE_MODE=v1, capture now retries 404 and 429 responses like 408 and 5xx instead of failing the batch at once. (2026-11-10)

5.68.1

Patch Changes

  • #5649 69b3cb8 Thanks @​marandaneto! - Fix empty OR and legacy cohort group matching, and fall back to the server for unsupported group types. (2026-11-10)

5.68.0

Minor Changes

  • #5642 21eb6bb Thanks @​rafaeelaudibert! - feat(node): let the NestJS interceptor take the request's distinct ID from a getDistinctId option or from identity already set in the PostHog context (2026-11-10)

5.67.2

... (truncated)

Commits
  • 79b1906 chore: update versions and lockfile [version bump]
  • 2877954 feat(emails): let a code send set its tracking and sensitivity (#5630)
  • 7dbe8de chore: update versions and lockfile [version bump]
  • b64482a feat(node): set a recipient's email topic preferences (#5511)
  • d669687 fix(metrics): export browser metrics once a minute by default (#5685)
  • d61b4f7 docs(node): regenerate the Node references for the React Email element (#5683)
  • 037175c chore: remove the HogRef reference generator (#5590)
  • 881c251 docs: add the generated browser, Node and React Native references (#5589)
  • 482422c feat: generate SDK references as Markdown with TypeDoc (#5588)
  • 43e895e chore: update versions and lockfile [version bump]
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 16, 2026
@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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

Run configuration

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

@github-actions
github-actions Bot enabled auto-merge (squash) November 16, 2026 04:05
Bumps [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) from 5.64.0 to 5.71.0.
- [Release notes](https://github.com/PostHog/posthog-js/releases)
- [Changelog](https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md)
- [Commits](https://github.com/PostHog/posthog-js/commits/posthog-node@5.71.0/packages/node)

---
updated-dependencies:
- dependency-name: posthog-node
  dependency-version: 5.71.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/posthog-node-5.71.0 branch from 157c66f to c6a719d Compare November 16, 2026 04:09
@github-actions
github-actions Bot merged commit 9525f54 into master Nov 16, 2026
6 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/posthog-node-5.71.0 branch November 16, 2026 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants