chore(deps): update dependency posthog-node to v5.49.0 - #246
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency posthog-node to v5.49.0#246renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
September 12, 2025 03:56
994ee7e to
bdaf96d
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
September 19, 2025 12:42
bdaf96d to
2ba2e03
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
September 20, 2025 12:22
2ba2e03 to
b079699
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
2 times, most recently
from
September 24, 2025 09:34
cffa922 to
a9221e7
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
2 times, most recently
from
September 29, 2025 10:12
eb94eb7 to
633a67a
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
October 7, 2025 00:38
633a67a to
11e3185
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
October 9, 2025 10:00
11e3185 to
ac71544
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
October 9, 2025 15:22
ac71544 to
0209997
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
October 14, 2025 13:33
0209997 to
a2d024b
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
2 times, most recently
from
October 21, 2025 23:13
0fa12e8 to
5e2f0fa
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
October 22, 2025 10:07
5e2f0fa to
5191aee
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
November 20, 2025 14:11
e25470a to
edaad1a
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
November 24, 2025 05:04
edaad1a to
b7a5456
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
November 24, 2025 10:12
b7a5456 to
848affd
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
2 times, most recently
from
November 28, 2025 15:06
036fcdc to
75c7b83
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 2, 2025 02:49
75c7b83 to
129f5c9
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 3, 2025 12:59
129f5c9 to
4b9064c
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 4, 2025 18:33
4b9064c to
f9d17dd
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 4, 2025 21:13
f9d17dd to
041534a
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 17, 2025 02:07
041534a to
de2958b
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 17, 2025 17:54
de2958b to
18cc58e
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 22, 2025 18:28
18cc58e to
3c00473
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
December 30, 2025 22:35
3c00473 to
721e553
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
January 6, 2026 04:43
721e553 to
a549316
Compare
renovate
Bot
force-pushed
the
renovate/posthog-node-5.x
branch
from
January 8, 2026 19:33
a549316 to
a64d5ec
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.29.2→5.49.0Release Notes
PostHog/posthog-js (posthog-node)
v5.49.0Compare Source
Minor Changes
c9086deThanks @carlos-marchal-ph! - Public betacaptureAi()/captureAiImmediate(): AI events on a dedicated isolated endpoint with the event UUID returned. NewenableFullAiCaptureoption replaces the internal_useAiLane/_enableMultimodalCapture; wrappers route through the AI endpoint and skip redaction/truncation when set (privacy mode still wins).(2026-08-13)
Patch Changes
c9086de]:v5.48.2Compare Source
Patch Changes
a77115bThanks @marandaneto! - Log shutdown timeouts without rejecting, and correct the Node.jsshutdown()return type toPromise<void>.(2026-08-12)
a77115b]:v5.48.1Compare Source
Patch Changes
#4346
4751b33Thanks @marandaneto! - Enforce configured request timeouts while consuming Capture V1 response bodies.(2026-08-06)
#4423
64ba193Thanks @marandaneto! - Use Node's zlib gzip implementation for Node SDK payloads to avoid sustained memory growth from frequent Web Streams compression.(2026-08-06)
Updated dependencies [
64ba193]:v5.48.0Compare Source
Minor Changes
fa3457fThanks @haacked! - Support thestarts_with,not_starts_with,ends_with, andnot_ends_withproperty filter operators in feature flag local evaluation. Matching is case-insensitive and mirrorsicontains, so flags using these operators no longer fall back to remote evaluation.(2026-08-05)
v5.47.11Compare Source
Patch Changes
3c40b6cThanks @marandaneto! - Keep request timeouts active through response body consumption and clarify eventual event UUID deduplication semantics.(2026-08-05)
3c40b6c]:v5.47.10Compare Source
Patch Changes
d3c4538Thanks @posthog! - Keep$referring_domainand canonicalutm_*/campaign parameters on minimal$feature_flag_calledevents. Previously the minimal allowlist stripped every campaign parameter, so a flag-called event landing first in a session could set the session's UTM attribution and channel type to NULL in web analytics.(2026-08-04)
d3c4538]:v5.47.9Compare Source
Patch Changes
facb4c1Thanks @marandaneto! - FixenableExceptionAutocapturesuppressing Node's default crash on unhandled promise rejections; fatal rejections instrictorwarn-with-error-codemode and rejections handled by anotherunhandledRejectionlistener are no longer captured.(2026-08-04)
v5.47.8Compare Source
Patch Changes
d4ffb83Thanks @marandaneto! - Schedule local feature flag polls after each request settles.(2026-08-04)
821a2c6]:v5.47.7Compare Source
Patch Changes
1cf9c6dThanks @marandaneto! - Bound stack source context reads and skip non-regular or oversized files.(2026-08-03)
v5.47.6Compare Source
Patch Changes
f3a71a1Thanks @marandaneto! - Clear completed lifecycle timeout handles so successful shutdowns do not leave timers running.(2026-08-03)
f3a71a1]:v5.47.5Compare Source
Patch Changes
eb0a793Thanks @ATKasem! - fix:personPropertiesandgroupPropertieson the feature flag methods are no longer typed asRecord<string, string>, so numeric and boolean values type-check without a cast. Local evaluation already handled them —matchPropertytakesRecord<string, any>and compares numerically forgt/gte/lt/lte— only the public types disagreed. These now use the sharedPropertiestype (personProperties?: Properties,groupProperties?: Record<string, Properties>), matchingsetPersonPropertiesForFlags/setGroupPropertiesForFlagsso theanycan be narrowed later. Types only, no runtime change.(2026-08-03)
eb0a793]:v5.47.4Compare Source
Patch Changes
7c3a9afThanks @marandaneto! - Preserve events added to a full queue while an earlier batch is being flushed.(2026-08-03)
7c3a9af]:v5.47.3Compare Source
Patch Changes
#4349
0e2b371Thanks @marandaneto! - Apply the feature flag definition request timeout while consuming the response body.(2026-07-31)
#4349
0e2b371Thanks @marandaneto! - Keep the feature flag definition request timeout active until the request settles.(2026-07-31)
v5.47.2Compare Source
Patch Changes
b9a241eThanks @ioannisj! - Fixidentify()leaving a user anonymous when the supplied ID already matches the persisted distinct ID (for example after a non-identified bootstrap seeded the same ID). The user is now marked identified and a person-processed$setevent is captured. Ports the same fix from posthog-js (browser) to the shared core used by React Native, Node, and posthog-js-lite.(2026-07-31)
b9a241e]:v5.47.1Compare Source
Patch Changes
3c40b6cThanks @marandaneto! - Keep request timeouts active through response body consumption and clarify eventual event UUID deduplication semantics.(2026-08-05)
3c40b6c]:v5.47.0Compare Source
Minor Changes
6e7f3aeThanks @ablaszkiewicz! - Emit the release id that posthog-cli injects into your bundle as$release_idon$exceptionevents, so PostHog can attach exceptions to a release without joining through symbol sets. AddsgetInjectedReleaseId()to@posthog/core. The property is only attached when an injected release id can be read.(2026-07-30)
Patch Changes
6e7f3ae]:v5.46.1Compare Source
Patch Changes
6c8fde0Thanks @hpouillot! - Normalize V8 Promise combinator stack frames so input indexes are not treated as source filenames.(2026-07-23)
6c8fde0]:v5.46.0Compare Source
Minor Changes
#4172
9621830Thanks @haacked! - send minimal$feature_flag_calledevents when the server enables itWhen the v2
/flagsresponse carriesminimalFlagCalledEvents: true(or, for posthog-node local evaluation, the flag-definitions payload carriesminimal_flag_called_events: true) and the evaluated flag is not linked to an experiment ($feature_flag_has_experiment === false),$feature_flag_calledevents are rebuilt from a strict allowlist of flag-evaluation, processing-control, and SDK-identity properties. Super properties,$set/$set_once, the$feature/<key>enumeration,$active_feature_flags, and the context envelope are stripped. Any missing signal (no gate on the response, bootstrapped or locally injected flags,has_experimentunknown) falls back to the full event, and experiment-linked flags always send the full envelope. The gate is stored alongside the cached flags (posthog-js persistence, posthog-node poller state) and is server-controlled, with no SDK-side configuration.before_sendruns after the filter and may re-add stripped properties. (2026-07-20)Patch Changes
9621830]:v5.45.2Compare Source
Patch Changes
06d19a2Thanks @dustinbyrne! - Avoid Next.js Edge runtime warnings for native compression and fatal error handling.(2026-07-16)
06d19a2]:v5.45.1Compare Source
Patch Changes
9eb2b28Thanks @dustinbyrne! - Fix the default Node.js event flush interval at 5 seconds.(2026-07-16)
v5.45.0Compare Source
Minor Changes
#4159
fad6d9aThanks @haacked! - add$feature_flag_has_experimentto$feature_flag_calledevents$feature_flag_calledevents now carry a$feature_flag_has_experimentboolean sourced from the server'shas_experimentflag metadata (the/flags?v=2response for remote evaluation, the/api/feature_flag/local_evaluationdefinitions for posthog-node local evaluation). The property is only sent when the server explicitly reportshas_experiment; it is omitted entirely when the value is unknown (older servers, missing metadata, bootstrapped or locally injected flags). (2026-07-16)Patch Changes
fad6d9a]:v5.44.0Compare Source
Minor Changes
fc2cb2eThanks @eli-r-ph! - Raise the defaultmaxQueueSizefrom 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 explicitmaxQueueSizeoption still overrides this default.(2026-07-15)
Patch Changes
fc2cb2e]:v5.43.0Compare Source
Minor Changes
#4117
1eddff7Thanks @DanielVisca! - add the posthog.metrics API (count, gauge, histogram) to posthog-node — alphaBackend services can now record metrics through the same statsd-style pre-aggregating client the browser SDK ships, with no OpenTelemetry setup:
Samples aggregate in memory and flush as OTLP/JSON to
/i/v1/metrics(one data point per series per window). Pending metrics are flushed onshutdown(). Core gains_sendMetricsBatchonPostHogCoreStateless(same outcome contract as_sendLogsBatch) and a sharedresolveMetricsConfig, so any core-based SDK can hostPostHogMetrics. (2026-07-15)Patch Changes
1eddff7]:v5.42.0Compare Source
Minor Changes
dc2aa5bThanks @posthog! - Expose the error tracking rate-limiter config via the newexceptionRateLimiterRefillRateandexceptionRateLimiterBucketSizeoptions. Burst protection is scoped per exception type (each distinct$exceptiontype gets its own token bucket, with no aggregate cap across types), so these let customers with high-cardinality exception types tune the per-type allowance.(2026-07-14)
Patch Changes
dc2aa5b]:v5.41.0Compare Source
Minor Changes
#4105
203284aThanks @eli-r-ph! - Add opt-in Capture V1 support. Set thePOSTHOG_CAPTURE_MODE=v1environment variable to submit analytics events to the Capture V1 endpoint (/i/v1/analytics/events) instead of the legacy/batch/endpoint, on both the batched and immediate send paths. The default remainsv0, so existing behavior is unchanged unless you opt in. Opt-in is env-var-only during the transition (no public option), so nothing on the API surface has to be removed when v1 later becomes the default.Capture V1 uses Bearer auth, lifts legacy
$-sentinel properties into a typedoptionsobject, and does per-event partial retry with exponential backoff clamped againstRetry-After. Dropped and undelivered events are surfaced on the clienterrorchannel as aCaptureV1Error.$ai_*events continue to use the legacy submitter for now, regardless of the capture mode.In
v1mode,$ai_*events are routed to an isolated in-memory queue and flushed independently of the Capture V1 queue, so the two transports never share a batch and a failure on one cannot re-send events already accepted on the other. Each queue keeps its own retry/durability semantics: the legacy queue re-queues on network failure (retrying on later flushes), while the V1 queue exhausts the sender's own attempt budget per cycle and then surfaces the failure rather than re-queuing. (2026-07-11)Patch Changes
203284a]:v5.40.0Compare Source
Minor Changes
0b49a4cThanks @turnipdabeets! - AddsecretKeyconfig as the canonical alias for the deprecatedpersonalApiKey(accepts a Personal API Key or Project Secret API Key).(2026-07-07)
v5.39.4Compare Source
Patch Changes
0c11747Thanks @marandaneto! - Stop duplicatingdistinct_idinside/flagsperson properties.(2026-07-02)
5e7e132]:v5.39.3Compare Source
Patch Changes
64e04baThanks @marandaneto! - Retry/flagsrequests that receive HTTP 502 or 504 responses across SDKs that use the shared core flags client.(2026-07-02)
64e04ba]:v5.39.2Compare Source
Patch Changes
a664b81Thanks @marandaneto! - Make Nodeflush()wait for pending asynchronous SDK work before draining the event queue, so events produced by helpers likecaptureException()are not missed. Pending work rejections no longer prevent queued events from flushing.(2026-07-01)
a664b81]:v5.39.1Compare Source
Patch Changes
#4029
b36b1ccThanks @marandaneto! - Callbefore_sendfor identify, group identify, and alias events.(2026-06-30)
#4027
ab118d2Thanks @marandaneto! - Safely serialize event batches with circular property references instead of crashing during flush.(2026-06-30)
Updated dependencies [
ab118d2]:v5.39.0Compare Source
Minor Changes
0063128Thanks @github-actions! - AddgroupIdentifyImmediate()to await the network request when identifying a group, mirroringcaptureImmediate/identifyImmediate/aliasImmediate. Useful in edge/serverless environments where the background queue may not flush. The Convex integration now uses it directly instead of routing$groupidentifythroughcaptureImmediate.(2026-06-30)
Patch Changes
0063128]:v5.38.8Compare Source
Patch Changes
08b404bThanks @mjfaga! - Fix local evaluation ignoring thein/not_inoperator on cohort-based flag conditions. "Not incohort" was evaluated as "in cohort", inverting cohort-exclusion flags. Now applies the operator to
the cohort membership result. (2026-06-29)
v5.38.7Compare Source
Patch Changes
619a25cThanks @marandaneto! - Retry feature flag requests after transient network errors only. The feature flag request retry count defaults to 1 and can be set to 0 to disable retries.(2026-06-29)
619a25c]:v5.38.6Compare Source
Patch Changes
606ef43Thanks @GauthierPLM! - Only stamp $groups from the top-levelgroupswhen present(2026-06-26)
v5.38.5Compare Source
Patch Changes
8e9689aThanks @marandaneto! - Dedupe feature flag called events per returned flag value.(2026-06-24)
8e9689a]:v5.38.4Compare Source
Patch Changes
6391106Thanks @dustinbyrne! - Respectdisable_capture_url_hasheswhen capturing Express and NestJS request URLs.(2026-06-23)
v5.38.3Compare Source
Patch Changes
4d59d0eThanks @marandaneto! - Deprecate the Node SDK Sentry integration and point users to PostHog Error Tracking for Node.(2026-06-23)
440e370]:v5.38.2Compare Source
Patch Changes
6b21f77Thanks @marandaneto! - Validate custom event UUID overrides and generate new UUIDs when invalid.(2026-06-19)
6b21f77]:v5.38.1Compare Source
Patch Changes
e6d7fe2Thanks @marandaneto! - Stop sending deprecated no-op top-leveltype,library, andlibrary_versionfields in event batch payloads. Useproperties.$libandproperties.$lib_versionfor SDK metadata; legacy queuedlibraryandlibrary_versionvalues are used as fallbacks when the official$properties are missing.(2026-06-18)
e6d7fe2]:v5.38.0Compare Source
Minor Changes
a0553b3Thanks @marandaneto! - AddsetPersonProperties()andunsetPersonProperties()helpers to manage person properties from the Node.js SDK.(2026-06-16)
Patch Changes
b3ec845,c6c163a]:v5.37.1Compare Source
Patch Changes
29bf8e3Thanks @marandaneto! - Add missing bugs metadata to package manifests.(2026-06-15)
29bf8e3]:v5.37.0Compare Source
Minor Changes
d6fc0a5Thanks @gustavohstrassburger! - feat(feature-flags): support theearly_exitcondition option in local evaluation. When a flag enables early exit, evaluation now stops and returnsfalseas soon as a condition group's property filters match but the rollout percentage excludes the user, instead of falling through to later groups — matching the server-side evaluation behavior.(2026-06-12)
v5.36.17Compare Source
Patch Changes
v5.36.16Compare Source
Patch Changes
25822ac]:v5.36.15Compare Source
Patch Changes
v5.36.14Compare Source
Patch Changes
612f97a]:v5.36.13Compare Source
Patch Changes
v5.36.12Compare Source
Patch Changes
v5.36.11Compare Source
Patch Changes
v5.36.10Compare Source
Patch Changes
v5.36.9Compare Source
Patch Changes
0c2acb9]:v5.36.8Compare Source
Patch Changes
v5.36.7Compare Source
Patch Changes
7820929Thanks @marandaneto! - Reduce duplicate internal code found by dry4ts.(2026-06-09)
v5.36.6Compare Source
Patch Changes
v5.36.5Compare Source
Patch Changes
v5.36.4Compare Source
Patch Changes
v5.36.3Compare Source
Patch Changes
v5.36.2Compare Source
Patch Changes
v5.36.1Compare Source
Patch Changes
v5.36.0Compare Source
Minor Changes
9287c87Thanks @turnipdabeets! - Add a configurable$is_serverevent property (defaulttrue) so PostHog can identify server-side events. SetisServer: falsewhen using the SDK as a client/CLI so the device OS is attributed normally.(2026-06-04)
v5.35.15Compare Source
Patch Changes
v5.35.14Compare Source
Patch Changes
v5.35.13Compare Source
Patch Changes
v5.35.12Compare Source
Patch Changes
v5.35.11Compare Source
Patch Changes
v5.35.10Compare Source
Patch Changes
v5.35.9Compare Source
Patch Changes
f3cc6faThanks @marandaneto! - Disable/no-op initialization paths instead of throwing or sending requests when PostHog project tokens are missing or blank.(2026-06-01)
3d4a76f]:v5.35.8Compare Source
Patch Changes
v5.35.7Compare Source
Patch Changes
d9ad199]:v5.35.6Compare Source
Patch Changes
7b84b75Thanks @ablaszkiewicz! - unify captureException in posthog core(2026-05-28)
7b84b75]:v5.35.5Compare Source
Patch Changes
v5.35.4Compare Source
Patch Changes
v5.35.3Compare Source
Patch Changes
5568f12]:v5.35.2Compare Source
Patch Changes
5d7a2d3Thanks @gustavohstrassburger! - Include group context in the $feature_flag_called deduplication key in _captureFlagCalledEventIfNeeded, so events fire independently per group combination.(2026-05-25)
v5.35.1Compare Source
Patch Changes
c806cca]:v5.35.0Compare Source
Minor Changes
18ea8b5Thanks @dustinbyrne! - Promote feature flag definition cache provider types to the mainposthog-nodeexport and deprecateposthog-node/experimentalimports.(2026-05-21)
Patch Changes
v5.34.10Compare Source
Patch Changes
f42f371Thanks @dmarticus! - Reject semver values with leading zeros in local flag evaluation. Per semver 2.0.0 §2, numeric identifiers must not include leading zeroConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.