Skip to content

Bump posthog-node from 5.42.0 to 5.44.0#772

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/posthog-node-5.44.0
Open

Bump posthog-node from 5.42.0 to 5.44.0#772
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/posthog-node-5.44.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 16, 2026

Copy link
Copy Markdown
Contributor

Bumps posthog-node from 5.42.0 to 5.44.0.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.44.0

5.44.0

Minor Changes

  • #4153 fc2cb2e Thanks @​eli-r-ph! - Raise the default maxQueueSize from 1000 to 10000. Backend workloads are more likely to burst-enqueue events synchronously ahead of a flush than browser/mobile clients, so the previous default risked silently dropping events under bursty load. An explicit maxQueueSize option still overrides this default. (2026-07-15)

Patch Changes

  • Updated dependencies [fc2cb2e]:
    • @​posthog/core@​1.42.1

posthog-node@5.43.0

5.43.0

Minor Changes

  • #4117 1eddff7 Thanks @​DanielVisca! - add the posthog.metrics API (count, gauge, histogram) to posthog-node — alpha

    Backend services can now record metrics through the same statsd-style pre-aggregating client the browser SDK ships, with no OpenTelemetry setup:

    const client = new PostHog('phc_...', { metrics: { serviceName: 'billing-worker' } })
    client.metrics.count('invoices.processed', 1, { attributes: { plan: 'pro' } })
    client.metrics.gauge('queue.depth', 42)
    client.metrics.histogram('job.duration', 187, { unit: 'ms' })

    Samples aggregate in memory and flush as OTLP/JSON to /i/v1/metrics (one data point per series per window). Pending metrics are flushed on shutdown(). Core gains _sendMetricsBatch on PostHogCoreStateless (same outcome contract as _sendLogsBatch) and a shared resolveMetricsConfig, so any core-based SDK can host PostHogMetrics. (2026-07-15)

Patch Changes

  • Updated dependencies [1eddff7]:
    • @​posthog/core@​1.42.0
Changelog

Sourced from posthog-node's changelog.

5.44.0

Minor Changes

  • #4153 fc2cb2e Thanks @​eli-r-ph! - Raise the default maxQueueSize from 1000 to 10000. Backend workloads are more likely to burst-enqueue events synchronously ahead of a flush than browser/mobile clients, so the previous default risked silently dropping events under bursty load. An explicit maxQueueSize option still overrides this default. (2026-07-15)

Patch Changes

  • Updated dependencies [fc2cb2e]:
    • @​posthog/core@​1.42.1

5.43.0

Minor Changes

  • #4117 1eddff7 Thanks @​DanielVisca! - add the posthog.metrics API (count, gauge, histogram) to posthog-node — alpha

    Backend services can now record metrics through the same statsd-style pre-aggregating client the browser SDK ships, with no OpenTelemetry setup:

    const client = new PostHog('phc_...', { metrics: { serviceName: 'billing-worker' } })
    client.metrics.count('invoices.processed', 1, { attributes: { plan: 'pro' } })
    client.metrics.gauge('queue.depth', 42)
    client.metrics.histogram('job.duration', 187, { unit: 'ms' })

    Samples aggregate in memory and flush as OTLP/JSON to /i/v1/metrics (one data point per series per window). Pending metrics are flushed on shutdown(). Core gains _sendMetricsBatch on PostHogCoreStateless (same outcome contract as _sendLogsBatch) and a shared resolveMetricsConfig, so any core-based SDK can host PostHogMetrics. (2026-07-15)

Patch Changes

  • Updated dependencies [1eddff7]:
    • @​posthog/core@​1.42.0
Commits
  • 004d79e chore: update versions and lockfile [version bump]
  • fc2cb2e feat(node): raise default maxQueueSize and drop-log severity (#4153)
  • 54b017c chore: update versions and lockfile [version bump]
  • 1eddff7 feat(metrics): wire posthog.metrics into posthog-node (#4117)
  • 6d9c314 chore: update versions and lockfile [version bump]
  • 6dd8827 fix(react-native): repeating surveys show again when a new iteration starts (...
  • See full diff in compare view

Dependabot compatibility score

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)

Bumps [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) from 5.42.0 to 5.44.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.44.0/packages/node)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 16, 2026
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