Closed wzieba closed 1 month ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Found 1 violations:
```diff +--- project :libs:analytics -| \--- com.automattic:Automattic-Tracks-Android:3.6.0 +| \--- com.automattic:Automattic-Tracks-Android:4.0.2 +--- project :libs:editor -| \--- com.automattic:Automattic-Tracks-Android:3.6.0 (*) +| \--- com.automattic:Automattic-Tracks-Android:4.0.2 (*) -\--- com.automattic:Automattic-Tracks-Android:{strictly 3.6.0} -> 3.6.0 (*) +\--- com.automattic:Automattic-Tracks-Android:{strictly 4.0.2} -> 4.0.2 (*) ```
Please review and act accordingly
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20545-293969a | |
Commit | 293969ad92c67924cadf39dab22eaff2e8b1e5c3 | |
Direct Download | wordpress-prototype-build-pr20545-293969a.apk |
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20545-293969a | |
Commit | 293969ad92c67924cadf39dab22eaff2e8b1e5c3 | |
Direct Download | jetpack-prototype-build-pr20545-293969a.apk |
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 40.24%. Comparing base (
569b0a4
) to head (293969a
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This pull request was deployed and Sentry observed the following issues:
org.wordpress.android.util.crashlogging.WPCrash...
View IssueDid you find this useful? React with a 👍 or 👎
Description
This PR bumps Tracks to
4.0.2
. The major change here is that we delegate creating a release name to Tracks library (Sentry internally), instead of providing value from our build config.This will address a problem of matching a release with the same name from different projects in the same Sentry organization.
Additionally, in debug/PR builds, we'll assign a
debug
release. This way, we'll clean up Sentry dashboard, as currently we have dozens of "pr-0000-00000" releases.To Test:
Screen from a test issue on release build type:
and on debug build type:
Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):