Repository navigation
chore(deps): update posthoganalytics to 7.83.1 - #128369
Conversation
|
😎 Merged successfully - details. |
|
Risk: No findings A pure dependency bump of posthoganalytics 7.82.2 → 7.83.1 across pyproject pins, uv.lock files, and two requirements files; no application code changes. I found no security issue: the lock diffs move only this package, and the SDK's flag-evaluation changes touch no authorization boundary in this repo. Sentinel reviewed |
![stamphog[bot]](https://avatars.githubusercontent.com/in/3000332?s=60&v=4){kind=small}
There was a problem hiding this comment.
Not approved — this change needs a human reviewer.
Re-adding the stamphog label gives the same result unless the changed files change.
stamphog can't auto-review this pull request because two gates refused it. The deny-list gate matched the deps_toolchain category, since the PR changes dependency pins and lockfiles (pyproject.toml, services/llm-gateway/pyproject.toml, both uv.lock files, and the two requirements.txt files). The tier gate classified it as T2-never because it is a cross-cutting chore touching six files across several services and tools.
The size and prerequisites gates passed, but they don't override the refusal. Please ask a human reviewer to look at this bump, and mention the existing release-bot PR for 7.83.0 so they can decide which one to take.
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✗ | matches: deps_toolchain |
| size | ✓ | 4L, 2F substantive, 24L/6F incl. docs/generated/snapshots — within ceiling |
| tier | ✗ | classified as T2-never: T2-never (24L, 6F, cross-cutting, chore) |
| stamphog 2.7.0 | .stamphog/policy.yml @ unknown · reviewed head 313ddf9 |
🤖 CI report
|
Problem
The app runs posthoganalytics 7.82.2. 7.83.0 moves remote flag evaluation to
/flags?v=4(PostHog/posthog-python#1031), and 7.83.1 adds an MCP fix (PostHog/posthog-python#1166). The app should run the current SDK.Changes
posthoganalytics(andposthogin the clitools requirements) from 7.82.2 to 7.83.1 in the same files the release bot updates, and bothuv.lockfiles. Onlyposthoganalyticsmoves in the locks.How did you test this code?
get_flags_decision, all flags and payloads, snapshots, single-flag getters andposthoganalytics.feature_enabled, for three identities, against a flags service with the v4 response off and one with it on. Values, payloads and$feature_flag_calledevents were identical, except the reason text of one new-format flag. Events were compared in memory, not sent.pytest posthog/query_scan/test/test_flag.py posthog/dags/tests/test_backfill_persons_on_events_mode.py posthog/hogql/test/test_metadata.pypasses.Test rationale: No new test: a dependency bump with no code change; the existing tests of the SDK call sites above cover it.
Release status
Docs update
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Agent: Claude Code, Claude Opus 5.5
Skills: None
More context for AI agents
posthoganalyticsis exempt from the repo's 7-dayexclude-newercutoff, souv lock --upgrade-package posthoganalyticsresolves it.🤖 Generated with Claude Code