Repository navigation
docs: pin the reference install line to the page's major - #1234
Conversation
posthog-python Compliance ReportDate: 2026-11-11T17:06:48.016165+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
|
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 |
1fa3af7 to
64311b6
Compare
Each generated reference page now installs the major it describes, so a reader of the 7.x page doesn't get 8.0 after it ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
64311b6 to
305fca0
Compare
💡 Motivation and Context
The 7.x and 8.x reference pages share one Getting started section, which says
pip install posthog. Once 8.0 ships, a reader of the 7.x page installs 8.0. Today a reader of the 8.x page installs 7.x. posthog.com docs pin installs to a major for the same reason. Stacked on #1233.docs/getting-started.mdwrites the install line as"posthog>={major},<{next_major}", and the generator fills in the page's major. The 7.x and reference pages get"posthog>=7,<8", and the 8.x page gets"posthog>=8,<9".{major}placeholder.Note
"posthog>=8,<9"matches no release until 8.0 publishes.💚 How did you test it?
posthog/test/test_reference_markdown.pychecks each major's pin. It fails when the install line is unpinned.📝 Checklist
If releasing new changes
sampo addto generate a changeset fileNo changeset: this changes the docs generator and generated pages only.
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Claude Code (Claude Opus 5.5).
🤖 Generated with Claude Code