Repository navigation
chore!: adopt posthog-android 4.0 - #663
Open
turnipdabeets wants to merge 1 commit into
Open
turnipdabeets wants to merge 1 commit into
turnipdabeets wants to merge 1 commit into
Conversation
6 tasks done
Contributor
posthog-flutter Compliance ReportDate: 2026-10-26 18:41:49 UTC ✅ All Tests Passed!45/45 tests passed Capture Tests✅ 29/29 tests passed View Details
Feature_Flags Tests✅ 16/16 tests passed View Details
|
turnipdabeets
marked this pull request as ready for review
October 23, 2026 17:05
turnipdabeets
force-pushed
the
chore/v6-adopt-posthog-ios-4
branch
from
October 26, 2026 18:36
c322313 to
852c2c9
Compare
turnipdabeets
force-pushed
the
chore/v6-adopt-posthog-android-4
branch
from
October 26, 2026 18:37
2aa9ae4 to
da3dedd
Compare
5 of 6 tasks
dustinbyrne
approved these changes
Oct 26, 2026
eli-r-ph
reviewed
Oct 26, 2026
| "posthog_flutter": major | ||
| --- | ||
|
|
||
| - **Breaking:** adopt `posthog-android` 4.x |
There was a problem hiding this comment.
Adopting posthog-android 4.0 moves Android events to capture v1 (/i/v1/analytics/events). A reverse proxy must forward the new path and the Authorization header, or events are dropped. Could the changeset say so and link the posthog-android 4.0 migration guide, as the Windows and Linux changeset does?
This branch has not been deployed
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_flutter 6.0 adopts posthog-android 4.0 (PostHog/posthog-android#871), so the 6.0 Flutter callbacks can carry the same flag data on Android as on iOS (see the stacked PR that passes the loaded flags to
onFeatureFlagsandreloadFeatureFlags).The Flutter Android plugin calls none of the APIs posthog-android 4.0 removes (
apiKey,propertiesSanitizer,evaluationEnvironments,getFeatureFlagPayload,debouncerDelayMs,remoteConfig) and none of the internal classes PostHog/posthog-android#872 makes non-public, so this is only the dependency range:[3.71.0,4.0.0)→[4.0.0,5.0.0).Merge order: like #649 for posthog-ios, this can't go green until posthog-android 4.0 is published. Merge it into #649's branch after that.
💚 How did you test it?
publishToMavenLocalof the 4.0 branch before marking this ready.📝 Checklist
If releasing new changes
pnpm changesetto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Claude Code (Claude Opus 5.5) checked the plugin's posthog-android usage against the 4.0 removals and the API narrowing in PostHog/posthog-android#872. Part of the feature flag parity work for the iOS, Android and Flutter majors.
🤖 Generated with Claude Code