fix(deps): update rust crate posthog-rs to 0.27.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
posthog-rs	dependencies	minor	0.22.0 → 0.27.0
posthog-rs	workspace.dependencies	minor	0.22.0 → 0.27.0

---

Release Notes

posthog/posthog-rs (posthog-rs)

v0.27.0

Compare Source

Minor changes

• fedcb87 Add optional async and blocking reqwest clients for sharing application HTTP configuration and connection pools across capture, feature flags, and local evaluation. SDK request and feature flag timeout options also apply to supplied clients. — Thanks @​marandaneto!

v0.26.0

Compare Source

Minor changes

• 6bc074f Honor definition snapshots' property_matching_version during local flag evaluation, including group conditions, recursive cohorts, and flag dependencies. Version 2 uses explicit case-insensitive equality instead of legacy boolean coercion; missing metadata and other versions retain legacy matching. Empty filters retain recursive truthiness in both versions. Keep matching semantics and definitions together across cache refreshes and version-only updates.

  LocalEvaluationResponse and EvaluationContext struct literals now require a property_matching_version field (use 1 for legacy behavior); older serialized definitions still load without it. The context-free match_feature_flag helper remains legacy. — Thanks @​marandaneto!

v0.25.5

Compare Source

Patch changes

• af85090 Do not panic when the HTTP client cannot be built. A container without CA certificates makes the reqwest builder fail, which stopped the calling program. The client now logs a warning, disables itself, and lets the program continue. The feature flag pollers degrade the same way: they log a warning and stay stopped instead of panicking. — Thanks @​posthog[bot]!

v0.25.4

Compare Source

Patch changes

• 20cf390 Match local feature flag properties with the same case folding, string coercion, and boolean-like filter precedence as the flags service. Substring and prefix/suffix operators now fold ASCII only, while exact and is_not use the service's truthiness handling before Unicode-lowercase comparison. — Thanks @​marandaneto!

v0.25.3

Compare Source

Patch changes

• 6d1a444 Treat omitted local evaluation properties as inconclusive for presence operators. — Thanks @​marandaneto!

v0.25.2

Compare Source

Patch changes

• e4ac827 Return an empty feature flag snapshot without evaluation when feature flag keys are explicitly empty. — Thanks @​marandaneto!

v0.25.1

Compare Source

Patch changes

• 253a7c0 Prevent transport worker deadlocks during client shutdown. — Thanks @​marandaneto!

v0.25.0

Compare Source

Minor changes

• 710ea93 Add group_identify helper to Client (async) and Client (blocking) for creating or updating group properties via $groupidentify. — Thanks @​vjymisal0 for your first contribution 🎉!

v0.24.0

Compare Source

Minor changes

• 7e2bede Add a Client::alias helper that merges two distinct IDs onto the same person, so callers no longer need to hand-build the $create_alias event and know that distinct_id is written both at the top level and inside properties. Available on the async and blocking clients with the same fire-and-forget signature as capture. A blank ID on either side cannot describe a merge, so the event is dropped with a warning rather than sent. — Thanks @​HughScott2002 for your first contribution 🎉!

v0.23.3

Compare Source

Patch changes

• f4e940d Normalize SDK timestamps to UTC — Thanks @​marandaneto!

v0.23.2

Compare Source

Patch changes

• ea92c93 Surface feature flag payloads from local evaluation.

  The definitions manifest carries each flag's payloads, but locally evaluated flags always reported payload: None, so FeatureFlagEvaluations::get_flag_payload returned nothing for them. When flag_keys was fully covered locally there was also no /flags round trip left to recover the payload from. Local evaluation now resolves the payload for the matched value ("true" for a boolean match, the variant key for a multivariate one) and decodes it exactly like a /flags payload, so a flag returns the same payload whichever path evaluated it. As a result, $feature_flag_called events for locally evaluated flags now carry $feature_flag_payload, matching remote evaluation. — Thanks @​slshults!

• 962282c Stop malformed cohort definitions from aborting the process during local evaluation.

  Cohort resolution recursed through nested cohort references with nothing bounding the recursion, so a cohort that referenced itself, directly or through another cohort, recursed until the thread stack was exhausted. A Rust stack overflow aborts the process rather than panicking catchably, so a single bad definitions response could take down the calling server, and would again on restart as soon as the poller refetched. A long chain of distinct cohorts reached the same abort without any cycle at all, and because each cohort is a separate shallow entry in the manifest, such a chain also cleared serde_json's own nesting limit on the way in.

  Cohort resolution now tracks the cohorts on the active resolution path and the combined depth of cohort references and nested property groups. A repeated cohort is reported as a cycle, and total resolution depth is capped at 100. Either is reported as inconclusive, so the flag falls back to server-side evaluation rather than resolving to a wrong value. Referencing the same cohort twice down sibling branches still resolves normally, since IDs are released as the recursion unwinds. — Thanks @​slshults!

v0.23.1

Compare Source

Patch changes

• cf8952a Fix local flag evaluation for projects that use cohorts.

  The /flags/definitions/?send_cohorts payload maps each cohort ID directly to its property group ({"type": "AND"|"OR", "values": [...]}), but Cohort required non-existent id/name/properties fields, so the whole LocalEvaluationResponse failed to deserialize and no flags loaded at all. Cohort now deserializes the real payload, and cohort matching recurses through nested AND/OR groups and cohort references instead of flattening them. — Thanks @​posthog[bot] for your first contribution 🎉!

v0.23.0

Compare Source

Minor changes

• 015e5a3 Add an atomic trace_context capture option and a client-level trace-context provider so exception events can be linked to distributed traces without adding telemetry dependencies to the SDK. — Thanks @​hpouillot for your first contribution 🎉!

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 these updates again.

---

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

---

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