[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
posthog-node (source)	5.56.2 → 5.57.2

---

Release Notes

PostHog/posthog-js (posthog-node)

v5.57.2

Compare Source

Patch Changes

• #​5422 b5036c4 Thanks @​posthog! - fix: esbuild no longer fails to bundle posthog-node when the optional @opentelemetry/api peer is not installed
  (2026-10-25)

v5.57.1

Compare Source

Patch Changes

• #​5385 faacff0 Thanks @​carlos-marchal-ph! - Apply the client privacyMode option to AI integrations, keep prompts out of errors, provider metadata and OTel spans in privacy mode, and redact MCP tool credentials
  (2026-10-23)

• #​5354 f827137 Thanks @​marandaneto! - Fall back instead of returning inconsistent local regex flag results for Unicode and advanced patterns.
  (2026-10-23)

• Updated dependencies [f827137]:

  • @​posthog/core@1.60.1

v5.57.0

Compare Source

Minor Changes

• #​5234 1991b99 Thanks @​gustavohstrassburger! - feat: report flags local evaluation could not resolve on evaluateFlags() snapshots via unresolvedFlags, tag reads of them with local_evaluation_inconclusive, and warn once about flags whose definition local evaluation does not support

  Behavior changes:

  • A condition with a filter local evaluation cannot check and a filter that does not match now resolves locally as no match, instead of falling back to a server request or staying unresolved.
  • $feature_flag_called events from snapshot reads report local_evaluation_inconclusive instead of flag_missing for these flags.
  • The load-time warning now also logs with strictLocalEvaluation: true. (2026-10-22)

Patch Changes

• Updated dependencies [1991b99]:
  • @​posthog/core@1.60.0

v5.56.4

Compare Source

Patch Changes

• #​5350 17260e5 Thanks @​marandaneto! - Fall back from local flag evaluation when a required property value is undefined.
  (2026-10-21)
• Updated dependencies [17260e5]:
  • @​posthog/core@1.59.3

v5.56.3

Compare Source

Patch Changes

• #​5307 189da75 Thanks @​quotentiroler! - Local flag evaluation now matches a null property with string operators like the flags service, so negated operators such as not_icontains match instead of failing.
  (2026-10-21)
• Updated dependencies [189da75]:
  • @​posthog/core@1.59.2

---

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one): 1

• coderabbit-review-active

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Zoo-Code-Org/Zoo-Code
• Branch: main
• File: .coderabbit.yaml
• Commit: 973cd13
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: f465802f-e39f-4c01-8b71-af784a023fae

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[github-actions]

Review status

This PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging.

Current step: The required review sequence passed. Remaining merge requirements apply.

Review-state labels are managed by this workflow; do not edit them manually. community-approved is managed the same way — do not add or remove it manually. It signals a fresh community code approval for the current head as an advisory priority only; maintainer review is still required.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!