Bump Realm from 10.3.0 to 10.5.0

[dependabot]

Bumps Realm from 10.3.0 to 10.5.0.

Release notes

Sourced from Realm's releases.

10.5.0

Enhancements

• ThreadSafeReference no longer pins the source transaction version for anything other than a Results backed by a Query. (Core upgrade)
• A ThreadSafeReference to a Results backed by a collection can now be created inside a write transaction as long as the collection was not created in the current write transaction. (Core upgrade)
• Synchronized Realms are no longer opened twice, cutting the address space and file descriptors used in half. (Core upgrade)

Fixed

• If an object with a null primary key was deleted by another sync client, the exception KeyNotFound: No such object could be triggered. (Core upgrade)
• Fixed a race condition that could result in an assertion m_state == SyncUser::State::LoggedIn if the app previously crashed during user logout. (Core upgrade)

Compatibility

• Realm Studio: 11.0.0 or later.

Internal

• Using Core 11.4.1.
• Added an action to post releases to Slack. (Issue #2501)
• Added MSBuild inline task to extract the changelog of the latest version. (Issue #2558)
• When a release succeeds, merge the original PR, tag the release, then update changelog. (PR #2609)

10.4.1

Fixed

• Fixed a regression that would prevent the SDK from working on older Linux versions. (Issue #2602)
• Fixed an issue that manifested in circumventing the check for changing a primary key when using the dynamic API - i.e. myObj.DynamicApi.Set("Id", "some-new-value") will now correctly throw a NotSupportedException if "some-new-value" is different from myObj's primary key value. (PR #2601)

Compatibility

• Realm Studio: 11.0.0 or later.

10.4.0 - Bug fixes and small improvements

Fixed

• Fixed an issue that would cause Logger.Default on Unity to always revert to Debug.Log, even when a custom logger was set. (Issue #2481)
• Fixed an issue where Logger.Console on Unity would still use Console.WriteLine instead of Debug.Log. (Issue #2481)
• Added serialization annotations to RealmObjectBase to prevent Newtonsoft.Json and similar serializers from attempting to serialize the base properties. (Issue #2579)
• Fixed an issue that would cause an InvalidOperationException when removing an element from an UI-bound collection in WPF. (Issue #1903)
• User profile now correctly persists between runs. (Core upgrade)
• Fixed a crash when delivering notifications over a nested hierarchy of lists of RealmValue that contain RealmObject inheritors. (Core upgrade)
• Fixed a crash when an object which is linked to by a RealmValue property is invalidated (sync only). (Core upgrade)
• Fixes prior_size history corruption when replacing an embedded object in a list. (Core upgrade)
• Fixed an assertion failure in the sync client when applying an AddColumn instruction for a RealmValue property when that property already exists locally. (Core upgrade)
• Fixed an Invalid data type assertion failure in the sync client when applying an AddColumn instruction for a RealmValue property when that property already exists locally. (Core upgrade)

Enhancements

• Added two extension methods on IList to get an IQueryable collection wrapping the list:

  • list.AsRealmQueryable() allows you to get a IQueryable<T> from IList<T> that can be then treated as a regular queryable collection and filtered/ordered with LINQ or Filter(string).
  • list.Filter(query, arguments) will filter the list and return the filtered collection. It is roughly equivalent to list.AsRealmQueryable().Filter(query, arguments).

  The resulting queryable collection will behave identically to the results obtained by calling realm.All<T>(), i.e. it will emit notifications when it changes and automatically update itself. (Issue #1499)

• Added a cache for the Realm schema. This will speed up Realm.GetInstance invocations where RealmConfiguration.ObjectClasses is explicitly set. The speed gains will depend on the number and complexity of your model classes. A reference benchmark that tests a schema containing all valid Realm property types showed a 25% speed increase of Realm.GetInstance. (Issue #2194)

• Improve performance of creating collection notifiers for Realms with a complex schema. In the SDKs this means that the first run of a synchronous query, first call to subscribe for notifications will do significantly less work on the calling thread.

• Improve performance of calculating changesets for notifications, particularly for deeply nested object graphs and objects which have List or Set properties with small numbers of objects in the collection.

• Query parser now accepts BETWEEN operator. Can be used like realm.All<Person>().Filter("Age BETWEEN {20, 60}") which means "'Age' must be in the open interval ]20;60[". (Core upgrade)

... (truncated)

Changelog

Sourced from Realm's changelog.

10.5.0 (2021-09-09)

Enhancements

• ThreadSafeReference no longer pins the source transaction version for anything other than a Results backed by a Query. (Core upgrade)
• A ThreadSafeReference to a Results backed by a collection can now be created inside a write transaction as long as the collection was not created in the current write transaction. (Core upgrade)
• Synchronized Realms are no longer opened twice, cutting the address space and file descriptors used in half. (Core upgrade)

Fixed

• If an object with a null primary key was deleted by another sync client, the exception KeyNotFound: No such object could be triggered. (Core upgrade)
• Fixed a race condition that could result in an assertion m_state == SyncUser::State::LoggedIn if the app previously crashed during user logout. (Core upgrade)

Compatibility

• Realm Studio: 11.0.0 or later.

Internal

• Using Core 11.4.1.
• Added an action to post releases to Slack. (Issue #2501)
• Added MSBuild inline task to extract the changelog of the latest version. (Issue #2558)
• When a release succeeds, merge the original PR, tag the release, then update changelog. (PR #2609)

10.4.1 (2021-09-03)

Fixed

• Fixed a regression that would prevent the SDK from working on older Linux versions. (Issue #2602)
• Fixed an issue that manifested in circumventing the check for changing a primary key when using the dynamic API - i.e. myObj.DynamicApi.Set("Id", "some-new-value") will now correctly throw a NotSupportedException if "some-new-value" is different from myObj's primary key value. (PR #2601)

Compatibility

• Realm Studio: 11.0.0 or later.

Internal

• Using Core 11.3.1.
• Started uploading code coverage to coveralls. (Issue #2586)
• Removed the [Serializable] attribute from RealmObjectBase inheritors. (PR #2600)

10.4.0 (2021-08-31)

Fixed

• Fixed an issue that would cause Logger.Default on Unity to always revert to Debug.Log, even when a custom logger was set. (Issue #2481)
• Fixed an issue where Logger.Console on Unity would still use Console.WriteLine instead of Debug.Log. (Issue #2481)
• Added serialization annotations to RealmObjectBase to prevent Newtonsoft.Json and similar serializers from attempting to serialize the base properties. (Issue #2579)
• Fixed an issue that would cause an InvalidOperationException when removing an element from an UI-bound collection in WPF. (Issue #1903)
• User profile now correctly persists between runs. (Core upgrade)
• Fixed a crash when delivering notifications over a nested hierarchy of lists of RealmValue that contain RealmObject inheritors. (Core upgrade)
• Fixed a crash when an object which is linked to by a RealmValue property is invalidated (sync only). (Core upgrade)
• Fixes prior_size history corruption when replacing an embedded object in a list. (Core upgrade)
• Fixed an assertion failure in the sync client when applying an AddColumn instruction for a RealmValue property when that property already exists locally. (Core upgrade)
• Fixed an Invalid data type assertion failure in the sync client when applying an AddColumn instruction for a RealmValue property when that property already exists locally. (Core upgrade)

Enhancements

• Added two extension methods on IList to get an IQueryable collection wrapping the list:

... (truncated)

Commits

• 02e9380 Prepare for 10.5.0 (#2614)
• 335aac2 Update to Core 11.4.1 (#2613)
• 7324e74 Add MSBuild task to extract changelog at build time (#2558)
• be789dc Wrap up the release workflow (#2609)
• 348ebba Cleanup self-hosted workspaces (#2610)
• c47ab70 Post to slack on release (#2608)
• e3a6948 Upgrade to latest Core (#2589)
• 3ee6708 Release 10.4.1 (#2606)
• 21a0137 Build Linux wrappers on docker (#2603)
• 3f6c966 Test net6 on win81 (#2605)
• 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 #32.