fix: send correct SDK user agent in analytics events - #246
Merged
Conversation
matthewelwell
approved these changes
Aug 31, 2026
4 tasks
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
2 participants
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.
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
The events flush sent
Flagsmith-SDK-User-Agent: flagsmith-python-client/{version}, while the flags client sendsflagsmith-python-sdk/{version}. The API only recognisesflagsmith-python-sdk, so analytics events were labelledsdk_label: unknown.DEFAULT_USER_AGENTnow lives inflagsmith/version.pyand is used by both code paths.How did you test this code?
Updated the existing header assertion in
tests/test_event_processor.py; full suite passes.