Repository navigation
ci: reuse Python SDK upgrade PRs unless queued - #1021
Merged
Merged
Conversation
Contributor
posthog-python Compliance ReportDate: 2026-10-06T21:58:30.739299+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
|
Contributor
|
[High risk] Changes CI workflow for dependency upgrade automation. Protect shared branches from overlapping runs and queued fallback collisions before merging. Reviews (1) · Last reviewed commit: "ci: reuse Python SDK upgrade PRs unless ..." |
turnipdabeets
approved these changes
Oct 7, 2026
3 of 5 tasks
eli-r-ph
pushed a commit
that referenced
this pull request
Oct 10, 2026
* ci: reuse Python SDK upgrade PRs unless queued * ci: protect reused upgrade PRs from stale and queued writes (cherry picked from commit 945bbbc)
eli-r-ph
pushed a commit
that referenced
this pull request
Oct 10, 2026
* ci: reuse Python SDK upgrade PRs unless queued * ci: protect reused upgrade PRs from stale and queued writes (cherry picked from commit 945bbbc)
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
Python SDK releases currently open a new downstream PostHog dependency PR for every version, leaving superseded updates open.
Match the JS updater's queue-aware reuse behavior:
PostHog/posthogPython upgrade PR, including existing version-named branches.posthoganalytics-upgradewhen no matching PR exists.PR discovery filters by title before applying the result limit, and the queue check reads all comment pages so it does not use a stale first-page status.
This changes only the downstream upgrade workflow. Package publishing and SDK runtime behavior are unchanged; no package release is needed. Existing superseded PRs are not closed by this change.
💚 How did you test it?
actionlintv1.7.7.bash -nand ShellCheck at warning severity.ghresponses in 14 scenarios: first PR, legacy/stable branch reuse, running/waiting queue, failed queue lookup, cleared queue status, unrelated comments, fork/unrelated-package exclusion, multiple matches, queue-status transitions beyond the first comment page, and failed PR lookup. All passed, along with title/body output wiring assertions.git diff --checkpassed.No live upgrade workflow was dispatched; branch pushes and PR updates performed by the workflow remain unverified end to end.
📝 Checklist
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Implemented with Pi, using Git/GitHub CLI for source inspection and local shell/YAML validation. The workflow follows the current JS updater's reuse and queue-protection pattern. A fresh read-only reviewer inspected the change before submission.