fossasia / phimpme-android

Phimp.me Photo Imaging and Picture Editor https://play.google.com/store/apps/details?id=org.fossasia.phimpme
GNU General Public License v3.0
2.58k stars 929 forks source link

build(deps): bump realm-gradle-plugin from 7.0.8 to 10.8.0 #3198

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps realm-gradle-plugin from 7.0.8 to 10.8.0.

Changelog

Sourced from realm-gradle-plugin's changelog.

10.8.0 (2021-08-27)

Enhancements

  • [RealmApp] ErrorCode.INVALID_EMAIL_PASSWORD has been added, and is now thrown instead of ErrorCode.SERVICE_UNKNOWN when loggin in with the wrong credentials.
  • RealmQuery.rawPredicate() now accepts a "BETWEEN" operator. Can be used like "age BETWEEN {20, 60}" which means "'Age' must be in the open interval ]20;60[".
  • [RealmApp] Added User.remove() and User.removeAsync() that makes it possible to delete a user's Realm(s) from the device.

Fixed

  • [RealmApp] Crash when integrating a schema from the server with a RealmAny property to a Realm File that already had that property defined locally. ([Realm Core #4873](realm/realm-core#4873), since 10.0.0)
  • [RealmApp] Refreshing the access token after 30 minutes would fail silently, causing infinite retries every 10 seconds. This would also block opening Realms when opening an app with an already logged in user. (Issue #7501, since 10.0.0)
  • [RealmApp] Clarified Javadoc for User.logOut() and User.logOutAsync() as these methods do not delete a user's Realm(s).
  • Build error when having cross module model references (Issue #7474, since v10.4.0)

Compatibility

  • File format: Generates Realms with format v22. Unsynced Realms will be upgraded from Realm Java 2.0 and later. Synced Realms can only be read and upgraded if created with Realm Java v10.0.0-BETA.1.
  • APIs are backwards compatible with all previous release of realm-java in the 10.6.y series.
  • Realm Studio 11.0.0-alpha.0 or above is required to open Realms created by this version.

Internal

  • Updated to Realm Core 11.3.0, commit: 321c79a67119db8177af13eefd5378586648ba73.

10.7.1 (2021-08-03)

Enhancements

  • None.

Fixed

  • [RealmApp] Crash when an object which is linked to by a RealmAny is invalidated (Sync only). ([Realm Core #4828](realm/realm-core#4828), since v10.6.0)
  • Object change listeners did not handle the object being deleted properly, which could result in assertion failures mentioning "m_table" in ObjectNotifier ([Realm Core #4824](realm/realm-core#4824), since v10.6.0).
  • Crash when delivering notifications over a nested hierarchy of lists of RealmAny that contain object references. ([Realm Core #4803](realm/realm-core#4803), since v10.6.0)

Compatibility

  • File format: Generates Realms with format v22. Unsynced Realms will be upgraded from Realm Java 2.0 and later. Synced Realms can only be read and upgraded if created with Realm Java v10.0.0-BETA.1.
  • APIs are backwards compatible with all previous release of realm-java in the 10.6.y series.
  • Realm Studio 11.0.0-alpha.0 or above is required to open Realms created by this version.

Internal

  • Updated to Realm Core 11.2.0, commit: 583fc73040709383470797813096bee17802398e.

10.7.0 (2021-07-27)

Breaking Changes

  • Removed automatic injection of repositories from Gradle plugin. From now on mavenCentral() repository needs to be added manually. (Issue #7365)

Enhancements

  • None.

Fixed

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)