Skip to content

chore(release): 0.7.1 #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Fiona2016 merged 1 commit into from
Sep 15, 2026
Merged

chore(release): 0.7.1 #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Unreleased
# 0.7.1 / 2026-09-14

* [FIX] RUM: send the running SDK's name in the remote configuration request instead of the literal `android`. A cross-platform wrapper sets the source to its own name (`react-native`, `flutter`, ...) and the native SDK already stamps that value on every event it sends; the configuration request was the one place that disagreed, so a configuration rule targeting the wrapper never matched the app running it. The same request already reported the wrapper's SDK version, which made a single request describe itself as two different SDKs. A native app is unaffected — the source falls back to `android` when no wrapper sets it. **Rollout note:** an app embedding a wrapper now sends the wrapper's name, so a rule written against `sdk=android` to reach such an app stops matching and has to be retargeted.

Expand Down
Loading