Repository navigation
Conversation
The published pages were generated from v1 as of 2026-11-04 and miss later 8.0 changes: per-event $lib, MCP and AI capture options, Celery context options and identity calls under a global personless setting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
posthog-python Compliance ReportDate: 2026-11-11T17:06:15.646886+00:00 ✅ All Tests Passed!270/270 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_V4 Tests✅ 149/149 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
gewenyu99
left a comment
There was a problem hiding this comment.
I will rewrite the migration guides later but this is good enough for launch :kek:
SDK performance: posthog-pythonBenchmarks completed. No changes flagged for review. Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate. View all results
Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals. Each shard uses its own runner; compare Before PR against With PR within a row, not across shards. Compared 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
💡 Motivation and Context
posthog.com serves
/docs/libraries/python/8.x.xand/docs/libraries/python/migrationfrom these files. They were generated fromv1as of 2026-11-04 (#1184), so the live migration page states 8.0 behavior that has since changed:$liband$lib_version, and that MCP events reportposthog-python. In 8.0 the SDK sends$libper event and keeps values you set, and MCP events reportposthog-python-mcp.posthog_options, and MCPevent_options.Changes:
v1at4f60c339, with #1182's docstring fixes and #1232's link fix applied. The migration page body isv1'sdocs/migration-7.x-to-8.0.mdwith docs: drop the GitHub link from the 8.0 guide's Celery eager note #1232.options,super_optionsand Celery'spropagate_context.The release-day rebuild regenerates both pages from the merged 8.0 code, which also carries
main's changes since 7.83.1. It keeps the link fix only if #1232 is merged.Note
The guide's link to
https://posthog.com/docs/libraries/capture-v1returns 404 until that page ships with 8.0. The live page has the same link.💚 How did you test it?
uv.lock) regeneratedmain's committed 7.x and reference pages byte for byte.v1with version 8.0.0, no--major) generates all three pages without errors.📝 Checklist
If releasing new changes
sampo addto generate a changeset fileNo changeset: this changes only generated reference pages.
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Claude Code (Claude Opus 5.5). Generated with
bin/docs_scripts/generate_markdown.py --major 8frommain, run on av1tree.🤖 Generated with Claude Code