chore(ci): automate PostHog Python SDK upgrades - #870
Merged
Conversation
Contributor
posthog-python Compliance ReportDate: 2026-08-13 12:47:03 UTC ✅ All Tests Passed!111/111 tests passed Capture_V1 Tests✅ 94/94 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
Member
Author
|
this is similar to posthog-js and posthog-rs already so nothing new |
Contributor
|
Reviews (1): Last reviewed commit: "chore(ci): automate PostHog Python SDK u..." | Re-trigger Greptile |
arnohillen
approved these changes
Aug 13, 2026
arnohillen
left a comment
There was a problem hiding this comment.
[arno's agent] Reviewed at head db8e055: change verified against head code, CI classified, no blocking findings.
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
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
PostHog uses the Python SDK under two distribution names. The application, LLM gateway, and ingestion tests use
posthoganalyticsto avoid colliding with PostHog's own Python package. The infra CLI installs the same SDK asposthog.New Python SDK releases currently require someone to update these declarations and both uv lockfiles manually. This adds a workflow that keeps every declaration on the released SDK version and opens a signed pull request in
PostHog/posthog.The release workflow dispatches the upgrade after publishing
posthoganalytics.💚 How did you test it?
actionlintagainst both changed workflows.📝 Checklist
If releasing new changes
sampo addto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Pi implemented the workflow from the existing
posthog-rsupgrade flow. The workflow treatsposthoganalyticsandposthogas distribution names for the same SDK release. It updates all six dependency and lock files in the PostHog repository and fails if any expected file remains unchanged.