Bump io.realm:realm-gradle-plugin from 10.11.1 to 10.15.0

[dependabot]

Bumps io.realm:realm-gradle-plugin from 10.11.1 to 10.15.0.

Changelog

Sourced from io.realm:realm-gradle-plugin's changelog.

10.15.0 (2023-04-19)

Breaking Changes

• Minimum version of Android Gradle Plugin has been raised to 7.4.
• Minimum version of Java has been raised to 11.
• Minimum supported version of Gradle has been raised to 7.5.

Enhancements

• None.

Fixed

• Building with Realm on Java 17 would fail with java.lang.IllegalAccessError: class io.realm.processor.Utils (in unnamed module @0x5316ec7f) cannot access class com.sun.tools.javac.code.Symbol$ClassSymbol. (Issue #7799)

Compatibility

• File format: Generates Realms with format v23. 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 13.0.0 or above is required to open Realms created by this version.
• Gradle 7.5 and above.
• Android Gradle Plugin 7.4.0 and above.

Internal

• None.

10.14.0-transformer-api (2023-04-14)

This release will bump the Realm file format from version 22 to 23. Opening a file with an older format will automatically upgrade it. Downgrading to a previous file format is not possible.

Breaking Changes

• [RealmApp] As a result of a refactor on the some error codes and categories have been deleted and new ones have been added, see PR for more details. (#7760)

Enhancements

• Updated OpenSSL from 1.1.1n to 3.0.8.
• Realm will now use a lot less memory and disk space when different versions of realm objects are used. (Core Issue #5440)
• Realm will now use a lot less memory and disk space when different versions of realm objects are used. (Core Issue #5440)
• Realm will now continuously track and reduce the size of the Realm file when it is in use rather that only when opening the file with Configuration.compactOnLaunch enabled. (Core Issue #5754)
• Multiple processes can now access the same encrypted Realm instead of throwing Encrypted interprocess sharing is currently unsupported. (Core Issue #1845)

Fixed

• Set consider string and binary data equivalent. This could cause the client to be inconsistent with the server if a string and some binary data with equivalent content was inserted from Atlas. (#4860, since v11.0.0)
• Fixed wrong assertion on query error that could result in a crash. (#6038, since v11.7.0)
• Fixed a bug that would result in RealmDictionary not being able to find double values due not taking the precision of the input parameter into consideration when using RealmDictionary.contains.
• Not possible to open an encrypted file on a device with a page size bigger than the one on which the file was produced. (#8030, since v12.11.0)
• Fix no notification for write transaction that contains only change to backlink property. (#4994, since v11.4.1)

Compatibility

• File format: Generates Realms with format v23. 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.

... (truncated)

Commits

• 63dca42 Release 10.15.0
• 17dd19d Fix Java 17 support (#7807)
• 2c02878 Update to Gradle 7.5 and AGP 7.4.0 (#7806)
• 148641c Merge pull request #7805 from realm/release/transformer-api
• 984b846 Update error message for incompatible AGP versions
• 7a66ba5 Merge transformer-api and main changelogs.
• 8aaef4f Track kotlin usage without inspecting configurations in configuration phase (...
• 1ea13b4 Prepare next dev iteration
• 21b3191 Release 10.14.0-transformer-api
• 752da80 Merge branch 'releases' into release/transformer-api
• Additional commits viewable in compare view

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)

[dependabot]

Superseded by #8349.