Update dependency posthog-node to v5.29.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
posthog-node (source)	5.28.5 → 5.29.2

---

Release Notes

PostHog/posthog-js (posthog-node)

v5.29.2

Compare Source

Patch Changes

• #​3351 c735b08 Thanks @​dmarticus! - Send $device_id as a top-level field in /flags requests so the feature flags service can use it for device-based bucketing during remote evaluation
  (2026-04-09)
• Updated dependencies [c735b08]:
  • @​posthog/core@​1.25.2

v5.29.1

Compare Source

Patch Changes

• Updated dependencies [57ee5b2]:
  • @​posthog/core@​1.25.1

v5.29.0

Compare Source

Minor Changes

• #​3302 fc5589f Thanks @​dmarticus! - preserve $set_once semantics in local flag evaluation cache
  (2026-04-07)

Patch Changes

• Updated dependencies [fc5589f]:
  • @​posthog/core@​1.25.0

v5.28.11

Compare Source

Patch Changes

• Updated dependencies [a01a3d5]:
  • @​posthog/core@​1.24.6

v5.28.10

Compare Source

Patch Changes

• #​3309 197eeda Thanks @​marandaneto! - Extract CLI and sourcemap utilities from @​posthog/core into @​posthog/plugin-utils to remove cross-spawn from React Native dependencies
  (2026-04-01)
• Updated dependencies [197eeda]:
  • @​posthog/core@​1.24.5

v5.28.9

Compare Source

Patch Changes

• Updated dependencies [a863914]:
  • @​posthog/core@​1.24.4

v5.28.8

Compare Source

Patch Changes

• Updated dependencies [4bdfdbc]:
  • @​posthog/core@​1.24.3

v5.28.7

Compare Source

Patch Changes

• Updated dependencies [8d34289]:
  • @​posthog/core@​1.24.2

v5.28.6

Compare Source

Patch Changes

• #​3282 5784dca Thanks @​marandaneto! - fix: captureException now uses distinctId from request context
  (2026-03-26)

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • Between 12:00 AM and 11:59 PM (* 0-23 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
adminv2	Ready	Preview, Comment	Apr 9, 2026 4:55am

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-beautiful-dnd@13.1.1
npm error Found: react@19.2.4
npm error node_modules/react
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error       node_modules/@mui/lab
npm error         @mui/lab@"^7.0.1-beta.19" from the root project
npm error       4 more (@mui/material, @mui/styled-engine, @mui/system, the root project)
npm error     peerOptional @emotion/react@"^11.5.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     5 more (@mui/material, @mui/styled-engine, @mui/system, ...)
npm error   peer react@">=16.8.0" from @emotion/styled@11.14.1
npm error   node_modules/@emotion/styled
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/material@7.3.9
npm error     node_modules/@mui/material
npm error       peer @mui/material@"^7.3.9" from @mui/icons-material@7.3.9
npm error       node_modules/@mui/icons-material
npm error         @mui/icons-material@"^7.3.5" from the root project
npm error       2 more (@mui/lab, the root project)
npm error     3 more (@mui/styled-engine, @mui/system, the root project)
npm error   29 more (@emotion/use-insertion-effect-with-fallbacks, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error node_modules/react-beautiful-dnd
npm error   react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error   node_modules/react-beautiful-dnd
npm error     react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-09T04_53_25_140Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-09T04_53_25_140Z-debug-0.log