-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Update target sdk version #920
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #920 +/- ##
======================================
Coverage 22% 22%
======================================
Files 136 136
Lines 3511 3511
======================================
Hits 746 746
Misses 2765 2765 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this should target the master
branch instead, because if we merge it on develop
, we wouldn't still comply with Google's policy at the end of the month
Well, since we won't need to hotfix anything on the release channel outside of the usual flow, the next time we update the release channel it will be from develop, so this will be there. Am I missing something? |
Maybe the wording on the Google Play Console is a bit weird, but it says: "You won't be able to release app updates". There's no real consequence of releasing an update which only updates the SDK version, so I prefer if we do it now ^^ |
I missed that discoverability part. Let me change the target branch then |
Yeah we can do that ^^ |
119e96e
to
e7ccb01
Compare
e7ccb01
to
800ce69
Compare
Bumps target version to comply with Google's policy.
Review checklist
whatsnew/whatsnew-pt-PT
changelog.md
with the change