-
-
Notifications
You must be signed in to change notification settings - Fork 735
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 gradle and other dependencies #1122
Conversation
Important notes: - minSDK set to API 28 as I prioritize security and adopting new standards over supporting old insecure platforms. - Old module GCM removed. - jacoco disabled as using the compiled version over jitpack leads to compilation errors which I could not fix so far.
…d + dependencies updated and unneeded anymore removed.
# [2.0.0](mobilekosmos/Parse-SDK-Android@1.26.0...2.0.0) (2021-10-12) ### Bug Fixes * remove GCM module ([#1091](https://github.com/mobilekosmos/Parse-SDK-Android/issues/1091)) ([aa16bcf](mobilekosmos@aa16bcf)) * upgrade Facebook SDK ([#1105](https://github.com/mobilekosmos/Parse-SDK-Android/issues/1105)) ([6f4bdb0](mobilekosmos@6f4bdb0)) ### Features * update all dependencies and modernize the source base ([#1095](https://github.com/mobilekosmos/Parse-SDK-Android/issues/1095)) ([a977d11](mobilekosmos@a977d11)) ### BREAKING CHANGES * CHANGE Support for Google Cloud Messaging (GCM) is removed, use Firebase Cloud Messaging instead. See the [Google developer documentation](https://developers.google.com/cloud-messaging/faq) for more details and migration assistance. ([aa16bcf](aa16bcf))
Thanks for opening this pull request!
|
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.
@mobilekosmos great job with this PR. I have missed some configurations regarding Jitpack and with #1095 my idea was not to update OkHttp or SDK version which you covered here - that's cool.
I left just few refactor comments.
Please let know when this is ready, so we can publish a release to fix #1124. |
It's ready for me. |
Could you please merge master into this and resolve the conflicts? The changes in the chagelog file can all be reverted, the changelog is generated automatically now. |
publishing { | ||
publications { | ||
// Creates a Maven publication called “debug”. | ||
debug(MavenPublication) { |
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.
Is this correct? It creates a maven publication "debug" but uses components "release".
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.
I think the name is not really relevant externally but I will double check.
Oh, I see there was a huge PR, waiting for an issue with it to be solved first. |
New Pull Request Checklist
Issue Description
Related issue: #
FILL_THIS_OUT
Approach
TODOs before merging