Update Proguard rules for GlobalDatadogTracer#3251
Merged
0xnm merged 1 commit intoMar 12, 2026
Conversation
kikoveiga
approved these changes
Mar 11, 2026
This comment has been minimized.
This comment has been minimized.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #3251 +/- ##
========================================
Coverage 71.37% 71.38%
========================================
Files 940 940
Lines 34764 34764
Branches 5893 5893
========================================
+ Hits 24812 24813 +1
- Misses 8298 8304 +6
+ Partials 1654 1647 -7
🚀 New features to boost your workflow:
|
0xnm
deleted the
nogorodnikov/update-proguard-rules-for-globaldatadogtracer
branch
March 12, 2026 07:24
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
3 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.
What does this PR do?
This PR fixes the following exception:
It is because of the
keepnamesusage, which a shorthand for-keep, allowshrinking: it will keep the name, but the method can still be shrinked. Switching to-keep, which won't allow method removal.Review checklist (to be filled by reviewers)