Repository navigation
docs: publish the posthog-python 8.x reference and migration guide pages - #1251
Conversation
Adds references/posthog-python-8.md and references/posthog-python-migration.md as the 8.0.0 release will write them, so the Strapi sync puts them on posthog.com before 8.0.0 ships. Both come from running bin/docs on docs/migration-guide-structure (#1245) with posthog/version.py at 8.0.0, the version the release sets before it generates. The generator on main writes only the 7.x page and the reference page, and skips the migration page without docs/migration-*.md, so neither file is rewritten before the release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
posthog-python Compliance ReportDate: 2026-11-13T18:19:32.609099+00:00 ✅ All Tests Passed!271/271 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✅ 150/150 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
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 |
PR overviewNo security issues were found in this pull request. Reviews
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ted lines Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
💡 Motivation and Context
This puts the posthog-python 8.x reference and the 7.x.x to 8.0.0 migration guide on posthog.com before 8.0.0 ships. The guide lives in #1245, which stacks on the unreleased v1 branch, so it can't reach
mainbefore the release.references/posthog-python-8.md. Becomes/docs/libraries/python/8.x.x.references/posthog-python-migration.md. Becomes/docs/libraries/python/migration.Both files are what the 8.0.0 release will write. I ran
bin/docsondocs/migration-guide-structurewithposthog/version.pyat8.0.0, the version the release sets before it generates, and with the latestPostHog/sdk-specs. The copies committed on that branch are behind it: the migration page still has a self-hosted paragraph its source dropped, and the 8.x page was titled as a pre-release.Generator code, workflows, and SDK code aren't touched.
posthog-python-reference.mdandposthog-python-7.mdstay asmainhas them, so/docs/libraries/python/referencekeeps showing 7.x until the release.Merge danger. Two-way door. A revert puts back
main's older 8.x page and migration guide, and the next Strapi sync publishes them again. Blast radius: the two pages above, which are both noindex.flowchart LR A["references/*.md on main"] --> B["squeak-strapi sdkMarkdownReferences cron"] B --> C["Strapi sdk-reference row"] C --> D["posthog.com onPreBootstrap writes contents/docs/libraries/python/*.md"]The sync reads
references/posthog-python-{reference,migration,N}.mdfrommain, so merging is all it takes to publish.Regeneration on
mainleaves both files alone.main'sbin/docs_scripts/generate_markdown.pywritesposthog-python-7.mdandposthog-python-reference.mdfor the declared major. It writesposthog-python-migration.mdonly whendocs/migration-*.mdexists, andmainhas none. Agenerate-references.ymldispatch or a 7.x release run can't rewrite or delete either file. When v1 lands, the release run regenerates both from the same sources.💚 How did you test it?
I ran posthog.com
masterlocally with these two files andmain'sreferenceand7pages at the pathsgatsby/onPreBootstrap.tswrites, then loaded each page.#links/docs/libraries/python/reference/docs/libraries/python/7.x.x/docs/libraries/python/8.x.x/docs/libraries/python/migrationEvery count matches the Markdown source, and no raw Markdown or front matter leaks into a page. The migration page links to
/docs/api/capture-v1, which 404s on posthog.com until PostHog/posthog.com#21385 merges. Console errors come only from site chrome.Screenshots, light mode
/docs/libraries/python/reference/docs/libraries/python/7.x.x/docs/libraries/python/8.x.x/docs/libraries/python/migration📝 Checklist
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Claude Code regenerated the pages from the guide branch at the release version, checked the generators and workflows on
main, and rendered the pages on a local posthog.com dev server.🤖 Generated with Claude Code