chore: let openfeature provider accept posthog 7 and 8

Author: eli-r-ph

.sampo/changesets/openfeature-provider-posthog-8.md

@@ -2,4 +2,4 @@
 pypi/openfeature-provider-posthog: minor
 ---
 
-Requires posthog 8.0 or later. Upgrade both packages together.
+Supports posthog 8.x as well as 7.x.

docs/migration-7.x-to-8.0.md

@@ -120,6 +120,7 @@ Two changes follow from this order:
   - `capture_ai_timeout`: default 30 seconds
   - `capture_ai_max_event_bytes`: default 8 MiB plus 64 KiB. You can only lower it.
 - `AsyncPosthog` has `capture_ai` and `capture_ai_immediate`.
+- `AsyncPosthog` accepts `privacy_mode` and `enable_full_ai_capture`, with the same meaning as on `Client`. An AI integration given an `AsyncPosthog` client used to always truncate and redact media.
 
 ## Batching and size limits
 
@@ -130,5 +131,5 @@ Two changes follow from this order:
 
 ## OpenFeature provider
 
-`openfeature-provider-posthog` 0.2.0 requires posthog 8.0 or later.
-Upgrade both packages together.
+`openfeature-provider-posthog` 0.2.0 works with posthog 7.x and 8.x.
+Older provider versions require posthog below 8.0, so upgrade the provider before or with posthog.

openfeature-provider/pyproject.toml

@@ -27,7 +27,7 @@ dependencies = [
     # single-call API. Pinned to the posthog major this provider is released and
     # tested against (both ship from this repo); bump the upper bound when moving
     # the provider to a new posthog major.
-    "posthog>=8.0.0,<9.0.0",
+    "posthog>=7.0.0,<9.0.0",
     "openfeature-sdk>=0.8.0",
 ]