chore(deps): bump posthog-node from 5.29.2 to 5.33.4

[dependabot]

Bumps posthog-node from 5.29.2 to 5.33.4.

Release notes

Sourced from posthog-node's releases.

posthog-node@5.33.4

5.33.4

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.28.4

posthog-node@5.33.3

5.33.3

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.28.3

posthog-node@5.33.2

5.33.2

Patch Changes

• #3516 220cd61 Thanks @​marandaneto! - fix: consume fetch response body to prevent CF Workers runtime warnings (2026-05-04)
• Updated dependencies [220cd61, 255b273]:
  • @​posthog/core@​1.28.2

posthog-node@5.33.1

5.33.1

Patch Changes

• Updated dependencies [8aee3d5]:
  • @​posthog/core@​1.28.1

posthog-node@5.33.0

5.33.0

Minor Changes

• #3476 f8bc02f Thanks @​dmarticus! - Add evaluateFlags() and a new flags option on capture() so a single /flags request powers both flag branching and event enrichment per incoming request:

  const flags = await posthog.evaluateFlags(distinctId, { personProperties: { plan: 'enterprise' } })
  if (flags.isEnabled('new-dashboard')) {
    renderNewDashboard()
  }
  posthog.capture({ distinctId, event: 'page_viewed', flags })

  The returned FeatureFlagEvaluations snapshot exposes isEnabled(), getFlag(), getFlagPayload() for branching, plus onlyAccessed() and only([keys]) for filtering which flags get attached to a captured event. Pass flagKeys: [...] to evaluateFlags() to scope the underlying /flags request itself. captureException() / captureExceptionImmediate() accept a flags argument so $exception events carry the same flag context as the rest of your request's events.

... (truncated)

Changelog

Sourced from posthog-node's changelog.

5.33.4

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.28.4

5.33.3

Patch Changes

• Updated dependencies []:
  • @​posthog/core@​1.28.3

5.33.2

Patch Changes

• #3516 220cd61 Thanks @​marandaneto! - fix: consume fetch response body to prevent CF Workers runtime warnings (2026-05-04)
• Updated dependencies [220cd61, 255b273]:
  • @​posthog/core@​1.28.2

5.33.1

Patch Changes

• Updated dependencies [8aee3d5]:
  • @​posthog/core@​1.28.1

5.33.0

Minor Changes

• #3476 f8bc02f Thanks @​dmarticus! - Add evaluateFlags() and a new flags option on capture() so a single /flags request powers both flag branching and event enrichment per incoming request:

  const flags = await posthog.evaluateFlags(distinctId, { personProperties: { plan: 'enterprise' } })
  if (flags.isEnabled('new-dashboard')) {
    renderNewDashboard()
  }
  posthog.capture({ distinctId, event: 'page_viewed', flags })

  The returned FeatureFlagEvaluations snapshot exposes isEnabled(), getFlag(), getFlagPayload() for branching, plus onlyAccessed() and only([keys]) for filtering which flags get attached to a captured event. Pass flagKeys: [...] to evaluateFlags() to scope the underlying /flags request itself. captureException() / captureExceptionImmediate() accept a flags argument so $exception events carry the same flag context as the rest of your request's events.

  Deprecates isFeatureEnabled(), getFeatureFlag(), getFeatureFlagPayload(), and capture({ sendFeatureFlags }). They continue to work but now log a deduped [PostHog] ... is deprecated warning the first time they're used. Removal is planned for the next major version. (2026-05-02)

5.32.1

... (truncated)

Commits

• 550b3bd chore: update versions and lockfile [version bump]
• fac0f9e chore: update versions and lockfile [version bump]
• 4b7edd3 chore: update versions and lockfile [version bump]
• e2f88e1 chore: update versions and lockfile [version bump]
• 2a1c739 chore: update versions and lockfile [version bump]
• f8bc02f feat(node): add evaluateFlags() API for single-call flag evaluation (#3476)
• c1ac939 chore: update versions and lockfile [version bump]
• b02194b chore: update versions and lockfile [version bump]
• 70ba8f8 feat(flags): support mixed targeting in local evaluation (#3474)
• eb5fc8e chore: update versions and lockfile [version bump]
• 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
pdfx	Ready	Preview, Comment	May 11, 2026 0:49am