build(deps): bump realm-gradle-plugin from 10.10.1 to 10.13.0-transformer-api

[dependabot]

Bumps realm-gradle-plugin from 10.10.1 to 10.13.0-transformer-api.

Changelog

Sourced from realm-gradle-plugin's changelog.

10.13.0-transformer-api (2012-12-12)

Enhancements

• [RealmApp] Added option for working with Device Sync from an internal network. SyncConfiguration.trustedRootCA(assetPath) can embed a custom certificate in the app that will be used by Sync. (Issue #7739).
• [RealmApp] Added option for working with Device Sync from an internal network. SyncConfiguration.disableSSLVerification() makes it possible to turn off local SSL validation. (Issue #7739).

Fixed

• Fixed database corruption and encryption issues on apple platforms. (Issue #5076)
• [Sync] Bootstraps will not be applied in a single write transaction - they will be applied 1MB of changesets at a time. (Issue #5999).
• [Sync] Fixed a race condition which could result in operation cancelled errors being delivered to Realm.open rather than the actual sync error which caused things to fail. (Issue #5968).

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 12.13.0, commit b77443ca7fa25407869ca537bf3ae912b1427bff.

10.12.0-transformer-api (2022-09-28)

Breaking Changes

• Only works with Android Gradle Plugin 7.4 or newer. (Issue #7714)

Enhancements

• [RealmApp] Introduced SyncSession.RecoverOrDiscardUnsyncedChangesStrategy, an alternative automatic client reset strategy that tries to automatically recover any unsynced data from the client, and discards any unsynced data if not possible. This is now the default client reset policy if not explicitly set in the SyncConfiguration.
• [RealmApp] Introduced SyncSession.RecoverUnsyncedChangesStrategy, an alternative automatic client reset strategy that tries to automatically recover any unsynced data from the client and will revert to manual client reset if not possible.
• [RealmApp] Flexible sync client reset is no longer limited to ManuallyRecoverChangesStrategy, it now supports all available strategies: RecoverOrDiscardUnsyncedChangesStrategy, RecoverUnsyncedChangesStrategy, DiscardUnsyncedChangesStrategy and ManuallyRecoverChangesStrategy.

Fixed

• Now queries can point to fields with query language-reserved words like 'desc', 'sort', 'distinct', etc. Issue #7705

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

• Update to Realm Core 12.6.0, commit: 5da7744b4056ad185c025bccf0924f17f73f7a91.

10.11.1 (2022-07-14)

Enhancements

• None

Fixed

• Fixed deadlock while trying to close all Realm instances during a manual client reset. Issue #7696)
• [RealmApp] Throw RuntimeException if subscription set is requested and flexible sync is not enabled. (Realm Core issue #5079)

... (truncated)

Commits

• 0d21bc2 Release 10.13.0-transformer-api
• cab2836 Merge commit '39d50f06ea9399e12a4680dd6f27e58544aa2d26' into release/transfor...
• 39d50f0 Release 10.13.0
• 0c61fc5 Update to core 12.13.0 (#7740)
• b6d1c94 Re-add custom certificate support (#7739)
• 8ed5f3e GitHub Workflows security hardening (#7728)
• 0fcea22 Release 10.12.0-transformer-api
• 259dda3 Add dependencies between native build tasks and Java header generation (#7729)
• fbc2197 Release 10.12.0-transformer-api
• d5cf550 Merge branch 'master' 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 #3341.