Repository navigation
Conversation
Contributor
posthog-python Compliance ReportDate: 2026-10-06T19:08:26.100214+00:00 ✅ All Tests Passed!121/121 tests passed Capture_V1 Tests✅ 95/95 tests passed View Details
Capture_Ai Tests✅ 5/5 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
3 of 5 tasks
eli-r-ph
marked this pull request as ready for review
October 7, 2026 20:43
This was referenced Oct 7, 2026
eli-r-ph
marked this pull request as draft
October 8, 2026 19:40
Contributor
Author
|
Putting this back in draft for safety as per the other SDK |
4 of 5 tasks
…nts (#1017) feat!: send capture through v1 by default; capture_ai posts to /i/v1/ai/events Capture v1 is now the default capture mode. The AI lane always posts capture v1 to /i/v1/ai/events, uncompressed, regardless of the analytics capture_mode. Tests move to a shared capture v1 send seam (posthog/test/capture_helpers.py); v0-only tests are pinned to CaptureMode.V0 until v0 removal.
Capture v1 is the only capture path. Remove CaptureMode, the capture_mode kwarg and POSTHOG_CAPTURE_MODE, the gzip kwarg, request.batch_post and the v0 endpoint constants, and the backoff dependency. Client and AsyncPosthog constructors are keyword-only after host.
Rename CaptureV1Error to CaptureError and export it from posthog. Event shaping moves to posthog.capture_event and transport to posthog.capture_send. No behavior change.
…1020) * feat!: report capture v1 results through CaptureError and on_error * test: cover _uuid7 layout for the mutation gate * fix: re-raise sync capture failures in debug mode after reporting them Also document which events verdict_summary() counts.
* feat: AI lane config and size-aware batching * chore: tighten AI lane comments * fix: reject non-finite AI lane config values
test(mcp): drop get_tool checks that fastmcp 4.0.11 invalidated fastmcp 4.0.11 resolves middleware-injected tools through the server's tool lookup (PrefectHQ/fastmcp#5431), so get_tool() now returns them. The two setup assertions that expected None fail on any fresh install. The SDK behavior the tests check is unchanged and passes on 4.0.10 and 4.0.11. (cherry picked from commit 897cd43) Co-authored-by: Claude Opus 5.5 <[email protected]>
feat!: per-event capture options and legacy property hoisting
* feat!: super_options, context options and personless as the lowest option layer * docs: state the option layer rules in capture docstrings * feat!: fill context and super values after before_send Context tags, context options, super_properties, super_options, the derived personless option and the environment $release_id now fill only keys an event leaves unset, after before_send runs. before_send sees only the event's own values and SDK enrichment, and its changes beat every default. A None option counts as unset and is filled. Legacy properties still fill only unset options and are always removed. * feat!: fill context and super values before before_send Context tags, context options, super_properties, super_options, the derived personless option and the environment $release_id now fill before before_send runs, still only into keys the event leaves unset. before_send sees every value and has the final say, including removing a super property. $set, $set_once, $groups and $group_set fill one level deep when both values are dicts. The set() and set_once() values now win key by key over a $set or $set_once in properties, as ingestion merges them. Hoisting still runs once, after the hook. * feat!: SDK values are defaults that caller values override $is_server, $geoip_disable and system context now fill last, only keys the event, context tags and super_properties left unset, before before_send. A super property $geoip_disable: False now wins over disable_geoip=True. The groups argument merges into a $groups property key by key and wins, in Client, AsyncClient and posthog.mcp events. * fix: copy async default layers at admission; typed groups win on MCP exception events AsyncPosthog filled defaults in the worker from references to the live super_properties and options, so a change after capture could reach a queued event. Each layer is now shallow-copied when the event is admitted, as 7.x merged super_properties into a new dict at capture. The MCP exception event now merges typed groups after custom properties, like the primary event, so both events of a failing call get the same groups. Co-Authored-By: Claude Opus 5.5 <[email protected]> --------- Co-authored-by: Claude Opus 5.5 <[email protected]>
feat!: AI wrappers and MCP send personless as a per-event option
* chore(ci): run compliance harness 1.13.1 once per codec The adapter now advertises capture_ai_v1 and event_options, passes options and uuids through unchanged, and takes its codec from COMPRESSION. The workflow runs the harness containers directly in a gzip/deflate/zstd matrix, so it no longer needs pull-requests: write. * chore(ci): install zstd extra for adapter protocol tests * chore: describe the single capture compliance job and harness 1.13.1 The standalone adapter-test setup installs the zstd extra, matching CI.
enable_full_ai_capture now controls only truncation and media redaction. A client object without capture_ai still gets capture calls.
* feat: AsyncPosthog AI capture lane * fix: type capture v1 send timeouts as float * feat: AsyncPosthog privacy_mode and enable_full_ai_capture * fix: keep async capture_ai from raising on a non-string event name
* test: capture invariant hardening * test: assert exactly one capture loss line per failed batch
* docs: 8.0 migration guide, README and openfeature-provider pin * chore: let openfeature provider accept posthog 7 and 8 * docs: say options beat legacy properties at every layer * docs: name the CaptureError import and the posthoganalytics mirror * docs: note that sync_mode failures re-raise in debug mode * docs: describe the late fill of context and super values * docs: describe the fill of context and super values before before_send * docs: SDK values are defaults that caller values override * docs: use real quota tags; a billing limit is a 402 Capture never sends billing_limit_exceeded or billing as a per-event tag. Product quotas drop single events in a 2xx with tags such as llm_events_over_quota; a request over the billing limit gets a 402 with no per-event results. * docs: complete the 8.0 migration guide * chore(examples): run the pinned AI examples against the local SDK
* feat!: keep the posthog-python identity when instrumenting MCP MCP instrumentation relabeled the whole client, so the app's own events and flag requests reported posthog-python-mcp. Capture v1 takes $lib from the per-request PostHog-Sdk-Info header, which is now always posthog-python. * chore: remove the unused request identity plumbing and stale MCP client advice
fix!: follow capture redirects only to the configured origin _post_v1 disables automatic redirects and resends the batch only on a 307 or 308 to the origin of host, at most 5 times. Any other redirect returns as a terminal failure. Covers the sync client and the async client, which lost its v0 same-origin guard when v1 became the only path.
* ci: reuse Python SDK upgrade PRs unless queued (#1021) * ci: reuse Python SDK upgrade PRs unless queued * ci: protect reused upgrade PRs from stale and queued writes (cherry picked from commit 945bbbc) * feat(error-tracking): standardize exception event metadata (#898) * feat(error-tracking): standardize exception metadata * fix(error-tracking): preserve explicit trace context * fix(error-tracking): restrict exception group traversal * fix(error-tracking): deprecate reserved property overrides * fix(error-tracking): bound exception group traversal (cherry picked from commit 6d6cc3d) * chore: Release v7.65.0 [skip ci] (cherry picked from commit c4e6bdd) * Update generated references (cherry picked from commit 50efa65) * feat(asgi): add error tracking middleware (#1037) * feat(asgi): add error tracking middleware * chore(asgi): type exception capture metadata * fix(asgi): make tracing header trust explicit * refactor(asgi): expose request properties terminology (cherry picked from commit 1c6a47a) * feat(mcp): resolve fresh low-level tool ownership (#1009) * feat(mcp): resolve fresh low-level tool ownership Add resolve_original_tool for raw MCP SDK 1.x and 2.x servers. Prefer ownership learned from a served listing and keep unknown ownership fail-open. Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e * fix(mcp): preserve listed argument ownership Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e * fix(mcp): preserve arguments for unknown schemas Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e * fix(mcp): preserve low-level tool schemas Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e (cherry picked from commit 127009d) * feat(flask): add error tracking integration (#1038) * feat(flask): add error tracking integration * fix(flask): use canonical exception metadata * chore(flask): type exception capture metadata * refactor(flask): expose request properties terminology * fix(flask): preserve exception privacy settings (cherry picked from commit 292855d) * chore: Release v7.66.0 [skip ci] (cherry picked from commit d23ef68) * Update generated references (cherry picked from commit c0e05b1) * feat(drf): add automatic error tracking integration (#1036) * feat(drf): add automatic error tracking integration * fix(drf): align exception metadata with SDK spec * chore(drf): type exception capture metadata * fix(drf): honor Django request filtering * test(drf): describe context data as properties * feat(drf): support exception capture opt-out * chore(drf): update public API snapshot * fix(drf): align exception capture configuration * test(drf): preserve omitted setting default (cherry picked from commit 9baf8a5) * chore: Release v7.67.0 [skip ci] (cherry picked from commit a655c8b) * Update generated references (cherry picked from commit 509c852) --------- Co-authored-by: Dustin Byrne <[email protected]> Co-authored-by: Hugues Pouillot <[email protected]> Co-authored-by: releaser-posthog-python[bot] <262414804+releaser-posthog-python[bot]@users.noreply.github.com> Co-authored-by: Georgis Andonis <[email protected]>
* fix: make request.post and request.flags arguments keyword-only * feat: add a level argument to capture_exception and ignore reserved exception properties * feat: warn when a non-string session or window id is dropped * docs: describe the exception level, keyword-only request args and session id warning * fix: warn once without the value when replacing an invalid event uuid An invalid caller uuid is still replaced with a generated UUIDv7, but the SDK now logs one warning that names the rule instead of an error that echoes the value. An empty string counts as unset and gets a generated uuid without a log. Client and AsyncClient share one helper. * fix: treat a per-call disable_geoip as a value of the event A disable_geoip argument now fills $geoip_disable as the event's own value: above context tags, super_properties and the client setting, and below a $geoip_disable in the call's properties. disable_geoip=False now sends $geoip_disable: false. Client and AsyncClient share the layer in _build_event_defaults.
* fix(ai): fail at setup when an AI integration's client lacks capture_ai * fix(ai)!: log and disable AI capture for a client without capture_ai Raising TypeError at construction could stop the host application over an analytics problem. The integration now logs one error at setup and captures no AI events; provider calls work and return normally. Co-Authored-By: Claude Opus 5.5 <[email protected]> --------- Co-authored-by: Claude Opus 5.5 <[email protected]>
* feat(mcp): set $mcp_interface on mcp analytics events (#1032) feat(mcp): add interface property to server events Generated-By: PostHog Desktop Task-Id: 651bf7d9-01f4-4d75-8583-868e29fdd314 (cherry picked from commit a3bd254) * chore: Release v7.67.1 [skip ci] (cherry picked from commit 4ae3d26) * Update generated references (cherry picked from commit 492d71b) * feat(integrations): align request middleware configuration (#1040) * Align ASGI and Flask integration defaults * feat(integrations): align request middleware configuration (cherry picked from commit 2f0d67d) * chore: Release v7.68.0 [skip ci] (cherry picked from commit ad553de) * Update generated references (cherry picked from commit 90f8d69) * chore(deps): bump the uv group across 2 directories with 3 updates (#1042) Bumps the uv group with 1 update in the /examples/example-ai-llamaindex directory: [banks](https://github.com/masci/banks). Bumps the uv group with 2 updates in the /examples/example-ai-pydantic-ai directory: [pydantic-ai](https://github.com/pydantic/pydantic-ai) and [pydantic-ai-slim](https://github.com/pydantic/pydantic-ai). Updates `banks` from 2.4.5 to 2.5.1 - [Release notes](https://github.com/masci/banks/releases) - [Commits](masci/banks@v2.4.5...v2.5.1) Updates `pydantic-ai` from 1.102.0 to 1.107.7 - [Release notes](https://github.com/pydantic/pydantic-ai/releases) - [Changelog](https://github.com/pydantic/pydantic-ai/blob/main/docs/changelog.md) - [Commits](pydantic/pydantic-ai@v1.102.0...v1.107.7) Updates `pydantic-ai-slim` from 1.102.0 to 1.107.7 - [Release notes](https://github.com/pydantic/pydantic-ai/releases) - [Changelog](https://github.com/pydantic/pydantic-ai/blob/main/docs/changelog.md) - [Commits](pydantic/pydantic-ai@v1.102.0...v1.107.7) --- updated-dependencies: - dependency-name: banks dependency-version: 2.5.1 dependency-type: indirect dependency-group: uv - dependency-name: pydantic-ai dependency-version: 1.107.7 dependency-type: direct:production dependency-group: uv - dependency-name: pydantic-ai-slim dependency-version: 1.107.7 dependency-type: indirect dependency-group: uv ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit ee686ff) * test(django): read the middleware context test's event after defaults fill On v1, context properties are filled inside _enqueue, before before_send. The test patched _enqueue itself, so it saw the event before the fill and lost $request_path and role. It now records the event in before_send. The assertions are unchanged. Co-Authored-By: Claude Opus 5.5 <[email protected]> * fix: redirect origin and logging fixes from review; scope AI routing docs - Compare redirect origins as requests sends them, so a Unicode host matches its IDNA form. - Log a refused or exhausted capture redirect at debug; failed-batch reporting owns warnings. - The migration guide says the OpenTelemetry integration still exports to /i/v0/ai/otel. Co-Authored-By: Claude Opus 5.5 <[email protected]> --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: Georgis Andonis <[email protected]> Co-authored-by: releaser-posthog-python[bot] <262414804+releaser-posthog-python[bot]@users.noreply.github.com> Co-authored-by: Hugues Pouillot <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <[email protected]>
* fix: drop only the invalid event, and size analytics by capture's limits An event with a missing, empty or non-string name, or one that cannot be serialized (for example with NaN), is dropped alone instead of failing the whole batch at capture. A property key JSON cannot represent is dropped from its event. The analytics per-event limit is capture's 10 MiB request limit, since capture reports an event over its per-event limit in the response. A personal API key disables the client like an empty key, and logs no longer include event content or invalid timestamp values. Co-Authored-By: Claude Opus 5.5 <[email protected]> * test: cover the event name, warn-once and personal key helpers in test_utils Co-Authored-By: Claude Opus 5.5 <[email protected]> * fix: keep the module client disabled for a personal API key; narrow two guide claims - setup() re-derived disabled from the key being non-empty, which re-enabled a client given a phx_ key on every module call. - The guide now says finite float keys are stringified (NaN keys drop the event) and that only the SDK's own log lines drop event content. Co-Authored-By: Claude Opus 5.5 <[email protected]> * docs: note the 200-byte event name limit in the 8.0 migration guide Co-Authored-By: Claude Opus 5.5 <[email protected]> * fix: drop an event whose before_send leaves a non-string distinct_id before_send can set any value, and capture v1 rejects the whole request for a non-string distinct_id. The SDK now drops that event locally with one warning per reason, and never converts the value or makes up an ID. Co-Authored-By: Claude Opus 5.5 <[email protected]> --------- Co-authored-by: Claude Opus 5.5 <[email protected]>
* fix: take group and alias ids from the caller, and apply request context by one rule group_identify uses the caller's distinct id, then the context id, then $<group_type>_<group_key>, never a random id, and no longer adds the context session id. alias() no longer takes its target from the context distinct id. Context tags and options now reach alias and group_identify like capture. An empty or whitespace-only distinct id counts as missing, and generated personless distinct ids are UUIDv7. Co-Authored-By: Claude Opus 5.5 <[email protected]> * docs: context reach for alias and group_identify; 200-byte distinct id limit Co-Authored-By: Claude Opus 5.5 <[email protected]> * docs: drop product_tour_id from the guide; name the legacy option properties Co-Authored-By: Claude Opus 5.5 <[email protected]> --------- Co-authored-by: Claude Opus 5.5 <[email protected]>
Clients that fail together now retry at slightly different times, so they do not all hit capture at once while it recovers. Retry-After still sets a minimum wait, and the 30 s cap still applies. Co-authored-by: Claude Opus 5.5 <[email protected]>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💡 Motivation and Context
Long-lived integration branch for posthog 8.0: capture v1 becomes the only capture path, and
capture_aimoves to an isolated v1 lane at/i/v1/ai/events. Feature PRs targetv1; this PR merges tomainonce the series lands. Do not merge.The
majorchangeset bumps the next release from 7.64.1 to 8.0.0.Series, stacked in merge order (each PR's base is the one before it, the first targets
v1):capture_aito/i/v1/ai/eventson a lane-aware v1 submitterhostcapture_v1module andCaptureV1ErrortoCaptureErrorsuper_options, context options, layer order and personless as an optioncapture_v1,capture_ai_v1,event_options), once per codeccapture_aiAsyncPosthogAI lane parity$libcomes only fromPostHog-Sdk-InfoRelated parity PRs: PostHog/posthog-go#359, PostHog/posthog-rs#279
mainis merged intov1periodically (no rebase, so open PRs keep their anchors).💚 How did you test it?
Changeset only. Each series PR carries its own tests.
📝 Checklist
If releasing new changes
sampo addto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Authored with Cursor (Claude Opus). Behavior follows the
v1branches of posthog-rs and posthog-go, adapted to this SDK's style.