chore(deps): bump posthog-node from 5.26.0 to 5.54.1

[dependabot]

Bumps posthog-node from 5.26.0 to 5.54.1.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.54.1

5.54.1

Patch Changes

• #4832 ac479db Thanks @​dustinbyrne! - Support snake_case feature flag cache payloads while preserving compatibility with camelCase providers and cached data. (2026-09-25)

posthog-node@5.54.0

5.54.0

Minor Changes

• #5099 e3955f8 Thanks @​marandaneto! - Expose feature flag evaluation reasons and preserve them in OpenFeature resolution metadata. (2026-09-25)

posthog-node@5.53.0

5.53.0

Minor Changes

• #5050 31dd1ad Thanks @​posthog! - Read a feature flag's evaluation runtime with getFeatureFlagEvaluationRuntime(key) and getFeatureFlagKeysByEvaluationRuntime(runtime) (2026-09-23)

posthog-node@5.52.6

5.52.6

Patch Changes

• #5078 f4704ac Thanks @​rubychilds! - Honor filters.holdout during local feature flag evaluation. A user in an experiment holdout now receives the holdout-<id> variant instead of being bucketed into a regular variant, matching how the server evaluates the same flag. The holdout is resolved before the release conditions, so a held-out user never reaches the flag's targeting — including when those conditions would have excluded them, so isFeatureEnabled can return true where it previously returned false. Experiments with an active holdout will see variant assignment change for the held-out share of traffic on upgrade, bringing locally evaluated assignments in line with server-evaluated ones. (2026-09-23)
• Updated dependencies [f4704ac]:
  • @​posthog/core@​1.55.2

posthog-node@5.52.5

5.52.5

Patch Changes

• #5018 9cd8ebd Thanks @​turnipdabeets! - Stop dropping long spans that end: maxSpanAgeMs now evicts spans only once maxLiveSpans is reached, so a span that runs past the age limit and then ends is exported, and its children are no longer orphaned. (2026-09-21)

• #4800 aad7464 Thanks @​marandaneto! - Respect the definitions response's property_matching_version during local feature flag evaluation. Version 2 uses explicit boolean/string equality and per-member array matching, while missing or other versions retain service legacy matching (including empty-array truthiness). Preserve the version in Node definition caches and Convex persisted definitions, and propagate it through person, group, cohort and dependency evaluation without mixing snapshots during reloads. Existing numeric ambiguity fallback and SemVer parsing policies are unchanged. (2026-09-21)

• Updated dependencies [9cd8ebd, aad7464]:

  • @​posthog/core@​1.55.1

posthog-node@5.52.4

5.52.4

... (truncated)

Changelog

Sourced from posthog-node's changelog.

5.54.1

Patch Changes

• #4832 ac479db Thanks @​dustinbyrne! - Support snake_case feature flag cache payloads while preserving compatibility with camelCase providers and cached data. (2026-09-25)

5.54.0

Minor Changes

• #5099 e3955f8 Thanks @​marandaneto! - Expose feature flag evaluation reasons and preserve them in OpenFeature resolution metadata. (2026-09-25)

5.53.0

Minor Changes

• #5050 31dd1ad Thanks @​posthog! - Read a feature flag's evaluation runtime with getFeatureFlagEvaluationRuntime(key) and getFeatureFlagKeysByEvaluationRuntime(runtime) (2026-09-23)

5.52.6

Patch Changes

• #5078 f4704ac Thanks @​rubychilds! - Honor filters.holdout during local feature flag evaluation. A user in an experiment holdout now receives the holdout-<id> variant instead of being bucketed into a regular variant, matching how the server evaluates the same flag. The holdout is resolved before the release conditions, so a held-out user never reaches the flag's targeting — including when those conditions would have excluded them, so isFeatureEnabled can return true where it previously returned false. Experiments with an active holdout will see variant assignment change for the held-out share of traffic on upgrade, bringing locally evaluated assignments in line with server-evaluated ones. (2026-09-23)
• Updated dependencies [f4704ac]:
  • @​posthog/core@​1.55.2

5.52.5

Patch Changes

• #5018 9cd8ebd Thanks @​turnipdabeets! - Stop dropping long spans that end: maxSpanAgeMs now evicts spans only once maxLiveSpans is reached, so a span that runs past the age limit and then ends is exported, and its children are no longer orphaned. (2026-09-21)

• #4800 aad7464 Thanks @​marandaneto! - Respect the definitions response's property_matching_version during local feature flag evaluation. Version 2 uses explicit boolean/string equality and per-member array matching, while missing or other versions retain service legacy matching (including empty-array truthiness). Preserve the version in Node definition caches and Convex persisted definitions, and propagate it through person, group, cohort and dependency evaluation without mixing snapshots during reloads. Existing numeric ambiguity fallback and SemVer parsing policies are unchanged. (2026-09-21)

• Updated dependencies [9cd8ebd, aad7464]:

  • @​posthog/core@​1.55.1

5.52.4

Patch Changes

• #4885 39a8980 Thanks @​decknamec! - Server-side feature flags now resolve in posthog-node and posthog-edge even when a proxy rewrites the request's User-Agent. Flags restricted to the client runtime now resolve to undefined in these SDKs, where a rewritten User-Agent previously let them through. (2026-09-15)
• Updated dependencies [39a8980]:
  • @​posthog/core@​1.54.2

... (truncated)

Commits

• 490ffe8 chore: update versions and lockfile [version bump]
• ac479db fix(node): support snake_case flag definition caches (#4832)
• 518ae78 chore: update versions and lockfile [version bump]
• e3955f8 feat: expose feature flag reasons in the Node OpenFeature provider (#5099)
• 7b3121f chore: update versions and lockfile [version bump]
• 31dd1ad feat(node): expose a flag's evaluation runtime through the SDK (#5050)
• 0c5557a chore: update versions and lockfile [version bump]
• f4704ac fix: honor filters.holdout in local flag evaluation (#5078)
• 3e72e7b chore: update versions and lockfile [version bump]
• aad7464 fix(flags): honor versioned local property matching (#4800)
• 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)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[netlify]

✅ Deploy Preview for thunderous-starship-f6b99a canceled.

Name	Link
🔨 Latest commit	1d07c14
🔍 Latest deploy log	https://app.netlify.com/projects/thunderous-starship-f6b99a/deploys/6abc5c4761b42c000800941b