Bump PostHog from 2.8.1 to 2.15.5

[dependabot]

Updated PostHog from 2.8.1 to 2.15.5.

Release notes

Sourced from PostHog's releases.

2.15.5

Patch Changes

• 2f38c21: Report package-specific library names and versions for ASP.NET Core and AI events.

2.15.4

Patch Changes

• bbb8d00: Allow local feature flag definitions with a null early_exit value.

2.15.3

Patch Changes

• eed813d: Fix async exception stack trace frames.

2.15.2

Patch Changes

• 5e2e606: Match local feature flag string operators using the same ASCII and Unicode lowercase rules as the flags service.

2.15.1

Patch Changes

• 22c61e1: Align local is_set and is_not_set evaluation with partial property context.

2.15.0

Minor Changes

• 071c6bb: Return an empty feature flag snapshot without evaluation work when FlagKeysToEvaluate is explicitly empty.

2.14.0

Minor Changes

• 4f2e3c8: Fall back to remote evaluation when a requested feature flag is missing from local definitions. This changes scoped calls from omitting the key without a request to making one direct /flags fallback per EvaluateFlagsAsync call.

2.13.3

Patch Changes

• 0c4094f: Support fractional rollout percentages when evaluating feature flags locally.

2.13.2

Patch Changes

• a5c6a22: Normalize captured event timestamps to the equivalent UTC instant.

2.13.1

Patch Changes

• 0c0fea0: Use the invariant culture when stringifying property values for feature flag local evaluation. Numeric property values such as 3.14 now stringify as "3.14" regardless of the host locale, so exact, icontains, starts_with, ends_with, and regex matching behave the same way the PostHog flags service does on machines using comma-decimal cultures.

2.13.0

Minor Changes

• 61b26a3: Support the starts_with, not_starts_with, ends_with, and not_ends_with property filter operators in feature flag local evaluation. Matching is case-insensitive and mirrors icontains, so flags using these operators no longer fail local evaluation.

  Property filter operators this SDK version doesn't recognize now deserialize as ComparisonOperator.Unknown instead of failing the entire local evaluation response, so only the affected flag falls back to remote evaluation.

2.12.2

Patch Changes

• 26057b5: Keep local feature flag evaluation available when is_set or is_not_set filters omit value, and support numeric values in filter arrays.

2.12.1

Patch Changes

• 2c2d89f: Prevent ProjectToken-only configuration from logging the deprecated ProjectApiKey warning.
• dd2b355: Avoid mutating caller-provided property dictionaries when capturing events, capturing exceptions, and using identify, group identify, page view, screen view, or survey capture helpers.

2.12.0

Minor Changes

• dd92ea1: Send minimal $feature_flag_called events when the server enables it (minimalFlagCalledEvents in the /flags v2 response or minimal_flag_called_events in the local evaluation payload) and the evaluated flag is not linked to an experiment. Minimal events keep a strict allowlist of flag evaluation properties and strip everything else, including the $feature/<key> enumeration and super properties. Experiment-linked flags and responses that do not carry the field continue to send the full event.

2.11.1

Patch Changes

• 90e0c94: Standardize event buffering defaults at a 10,000-event queue, 100-event flush threshold, 100-event maximum batch size, and 5-second flush interval.

2.11.0

Minor Changes

• a329a13: Add a $feature_flag_has_experiment boolean property to $feature_flag_called events when the server reports whether the flag is linked to an experiment. The property is omitted when the server does not report it (older deployments and legacy response formats).

2.10.0

Minor Changes

• d9d59a5: Add PostHogOptions.SecretKey for local feature flag evaluation and remote config. It accepts either a Personal API Key (phx_...) or a Project Secret API Key (phs_...). The existing PersonalApiKey option is now a deprecated alias; when both are set, SecretKey takes precedence.

2.9.0

Minor Changes

• d543f28: Add a before send callback for modifying or dropping fully enriched events.

2.8.7

Patch Changes

• 048601e: Stop duplicating distinct_id inside /flags person properties.

2.8.6

Patch Changes

• c631799: Retry remote feature flag requests after transient 502 and 504 responses.

2.8.5

Patch Changes

• 256d2df: Add a per-client circuit breaker for feature flag requests after consecutive transient network failures, temporarily failing fast before probing for recovery.

2.8.4

Patch Changes

• 211aa24: Add a feature flag request option for disabling GeoIP enrichment.

2.8.3

Patch Changes

• 7bab8dc: Fall back to uncompressed batch uploads when local gzip compression fails.

2.8.2

Patch Changes

• 0da29c6: Retry feature flag requests after transient network errors only. The feature flag request retry count defaults to 1 and can be set to 0 to disable retries.

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)