chore(flags): bump posthog-analytics to 7.10.2

[patricio-posthog]

Summary

Bumps posthoganalytics from 7.9.12 to 7.10.2 to pick up the configurable local evaluation endpoint feature. This is the final step to route PostHog's internal SDK polling from Django to the Rust /flags/definitions endpoint.

Context

This is part of the migration to the new Rust endpoint for local eval. Three PRs work together:

1. Python SDK: chore: configurabel endpoint for flags local evaluation posthog-python#483 adds POSTHOG_LOCAL_EVALUATION_ENDPOINT env var support with fallback to Django
2. Charts: https://github.com/PostHog/charts/pull/9713 sets POSTHOG_LOCAL_EVALUATION_ENDPOINT=/flags/definitions on all Django pods
3. This PR bumps the SDK version so production picks up the new endpoint logic

Changes

• pyproject.toml: posthoganalytics==7.9.12 to posthoganalytics==7.10.2, added posthoganalytics to exclude-newer-package (release is <7 days old)
• uv.lock: updated lockfile

What happens after merge

PostHog's Django pods will start polling /flags/definitions on the Rust definitions fleet instead of /api/feature_flag/local_evaluation on Django. If the Rust endpoint fails, the SDK falls back to Django transparently.

What to monitor

• flags_flag_definitions_requests_total on the definitions fleet — should go from 0 to active
• flags_flag_definitions_cache_hit_total — should see hits
• No increase in 5xx rates
• Dashboard: "Feature Flags - Rust Local Evaluation"

Rollback

Remove POSTHOG_LOCAL_EVALUATION_ENDPOINT from charts common.yaml. The SDK falls back to Django automatically, no need to revert this version bump.

[greptile-apps]

Vulnerabilities

No security concerns identified. The lockfile hashes and PyPI URLs are consistent with a legitimate version bump of the first-party posthoganalytics package.

_{Reviews (1): Last reviewed commit: "chore(flags): bump posthog-analytics to ..." | Re-trigger Greptile}

[gantoine]

makes sense since it's an internal package 👍🏼

[tests-posthog]

⏭️ Skipped snapshot commit because branch advanced to 1ce24c3 while workflow was testing 0a12b46.

The new commit will trigger its own snapshot update workflow.

If you expected this workflow to succeed: This can happen due to concurrent commits. To get a fresh workflow run, either:

• Merge master into your branch, or
• Push an empty commit: git commit --allow-empty -m 'trigger CI' && git push

[tests-posthog]

⏭️ Skipped snapshot commit because branch advanced to af44e4d while workflow was testing 1ce24c3.

The new commit will trigger its own snapshot update workflow.

If you expected this workflow to succeed: This can happen due to concurrent commits. To get a fresh workflow run, either:

• Merge master into your branch, or
• Push an empty commit: git commit --allow-empty -m 'trigger CI' && git push

[tests-posthog]

Query snapshots: Backend query snapshots updated

Changes: 1 snapshots (1 modified, 0 added, 0 deleted)

What this means:

• Query snapshots have been automatically updated to match current output
• These changes reflect modifications to database queries or schema

Next steps:

• Review the query changes to ensure they're intentional
• If unexpected, investigate what caused the query to change

Review snapshot changes →

[github-actions]

✅ Hobby deploy smoke test: PASSED

Hobby deployment smoke test passed successfully.

---

_{Run 24158149078}

[github-actions]

🎭 Playwright report · View test results →

⚠️ 2 flaky tests:

• Save view (chromium)
• Materialize view pane (chromium)

These issues are not necessarily caused by your changes.
Annoyed by this comment? Help fix flakies and failures and it'll disappear!

[tests-posthog]

⏭️ Skipped snapshot commit because branch advanced to f83a9f4 while workflow was testing 32f075b.

The new commit will trigger its own snapshot update workflow.

If you expected this workflow to succeed: This can happen due to concurrent commits. To get a fresh workflow run, either:

• Merge master into your branch, or
• Push an empty commit: git commit --allow-empty -m 'trigger CI' && git push

[tests-posthog]

⏭️ Skipped snapshot commit because branch advanced to 32a8708 while workflow was testing f83a9f4.

The new commit will trigger its own snapshot update workflow.

If you expected this workflow to succeed: This can happen due to concurrent commits. To get a fresh workflow run, either:

• Merge master into your branch, or
• Push an empty commit: git commit --allow-empty -m 'trigger CI' && git push