Repository navigation
ci: keep dependabot from raising uv/pip manifest floors - #1219
Conversation
posthog-python Compliance ReportDate: 2026-11-10T08:23:31.951342+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-python2 changes worth reviewing: 2 observed regressions. 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
|
There was a problem hiding this comment.
Approved.
Contained dependency-update configuration tweak; it changes neither dependencies themselves nor CI execution. No open review concerns or other refusal grounds.
- PostHog Review (Standard) reviewed the current head: no findings.
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 2L, 1F substantive — within ceiling |
| tier | ✓ | T0 auto-approve: T0-deterministic (2L, 1F, single-area, ci) |
| stamphog 2.7.0 | .stamphog/policy.yml @ 132bce2 · reviewed head 132bce2 |
💡 Motivation and Context
Follow-up to PostHog/posthog-flutter#641, where Manoel asked if this should go to all SDKs.
Dependabot's default strategy raises the manifest floor on every bump, even when the current range already allows the new version. For a library that floor is what consumers inherit, so each bump forces them up with nothing gained on our side.
versioning-strategy: increase-if-necessarykeeps the lockfile moving (CI still runs against the newer version) and only touches the manifest when the release falls outside the current range. It's been on posthog-flutter for a month: 3 pub PRs since, none touched the published manifest.Only the
uvandpipblocks change. GitHub Actions keeps its weekly bumps.💚 How did you test it?
I parsed the yaml and checked the key sits under the
uvandpipblocks only. I didn't dry-run dependabot's CLI.📝 Checklist
If releasing new changes
sampo addto generate a changeset file🤖 Agent context
DRI: @ioannisj
Autonomy: Human-driven (agent-assisted)