[Snyk] Upgrade realm from 12.4.0 to 12.5.0

[zepor]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade realm from 12.4.0 to 12.5.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 21 days ago, on 2023-12-19.

Release notes

Package name: realm

• 12.5.0 - 2023-12-19
  

  Enhancements

  • Added an optional third keyPaths argument to the addListener methods of Collection and Object. Use this to indicate a lower bound on the changes relevant for the listener. This is a lower bound, since if multiple listeners are added (each with their own "key paths") the union of these key-paths will determine the changes that are considered relevant for all listeners registered on the object or collection. In other words: A listener might fire more than the key-paths specify, if other listeners with different key-paths are present. (#6285)

    // Adding a listener that will fire only on changes to the `location` property (if no other key-path listeners are added to the collection).
    cars.addListener((collection, changes) => {
      console.log("A car location changed");
    }, ["location"]);

  • Exceptions thrown during bootstrap application will now be surfaced to the user via the sync error handler rather than terminating the program with an unhandled exception. (realm/realm-core#7197)

  Fixed

  • Exceptions thrown during bootstrap application could crash the sync client with an !m_sess assertion. (realm/realm-core#7196, since v10.18.0)
  • If a SyncSession was explicitly resumed via reconnect() while it was waiting to auto-resume after a non-fatal error and then another non-fatal error was received, the sync client could crash with a !m_try_again_activation_timer assertion. (realm/realm-core#6961, since device sync was introduced)
  • Adding the same callback function as a listener on a Collection or Object used to be undefined behavior. Now it throws, which results in runtime errors that can be resolved by ensuring that the callback is only added once per object. (#6310)

  Compatibility

  • React Native >= v0.71.4
  • Realm Studio v14.0.0.
  • File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

  Internal

  • Upgraded Realm Core from v13.24.1 to v13.25.0. (#6324)
• 12.4.0 - 2023-12-13
  

  Enhancements

  • Exporting a RealmEventName type. (#6300)
  • Automatic client reset recovery now preserves the original division of changesets, rather than combining all unsynchronized changes into a single changeset. (realm/realm-core#7161)
  • Automatic client reset recovery now does a better job of recovering changes when changesets were downloaded from the server after the unuploaded local changes were committed. If the local Realm happened to be fully up to date with the server prior to the client reset, automatic recovery should now always produce exactly the same state as if no client reset was involved. (realm/realm-core#7161)
  • Improved the experience of logging Realm.Object and Realm.Collection objects on Node.js, by providing a custom "inspect" symbol. (#2758)

  Fixed

  • When mapTo is used on a property of type List, an error like Property 'test_list' does not exist on 'Task' objects occurs when trying to access the property. (#6268, since v12.0.0)

  • Fixed bug where apps running under JavaScriptCore on Android will terminate with the error message No identifiers allowed directly after numeric literal. (#6194, since v12.2.0)

  • When an object had an embedded object as one of its properties, updating that property to null or undefined did not update the property in the database. (#6280, since v12.0.0)

  • Fixed download of platform + arch specific prebuilt binaries when building an Electron app using electron-builder. (#3828)

  • Fixed deadlock which occurred when accessing the current user from the App from within a callback from the User listener. (realm/realm-core#7183, since v12.2.1)

  • Errors encountered while reapplying local changes for client reset recovery on partition-based sync Realms would result in the client reset attempt not being recorded, possibly resulting in an endless loop of attempting and failing to automatically recover the client reset. Flexible sync and errors from the server after completing the local recovery were handled correctly. (realm/realm-core#7149, since v10.3.0-rc.1)

  • During a client reset with recovery when recovering a move or set operation on a List<Object> or List<Mixed> that operated on indices that were not also added in the recovery, links to an object which had been deleted by another client while offline would be recreated by the recovering client. But the objects of these links would only have the primary key populated and all other fields would be default values. Now, instead of creating these zombie objects, the lists being recovered skip such deleted links. (realm/realm-core#7112 since the beginning of client reset with recovery in v10.18.0)

  • During a client reset recovery a Set of links could be missing items, or an exception could be thrown that prevents recovery e.g., Requested index 1 calling get() on set 'source.collection' when max is 0. (realm/realm-core#7112, since the beginning of client reset with recovery in v10.18.0)

  • Calling sort() or distinct() on a LnkSet that had unresolved links in it would produce duplicate indices. (realm/realm-core#7112, since the beginning of client reset with recovery in v10.18.0)

  • Automatic client reset recovery would duplicate insertions in a list when recovering a write which made an unrecoverable change to a list (i.e. modifying or deleting a pre-existing entry), followed by a subscription change, followed by a write which added an entry to the list. (realm/realm-core#7155, since v10.19.4)

  • Fixed several causes of "decryption failed" exceptions that could happen when opening multiple encrypted Realm files in the same process while using Apple/linux and storing the Realms on an exFAT file system. (realm/realm-core#7156, since v1.0.0)

  • If the very first open of a flexible sync Realm triggered a client reset, the configuration had an initial subscriptions callback, both before and after reset callbacks, and the initial subscription callback began a read transaction without ending it (which is normally going to be the case), opening the frozen Realm for the after reset callback would trigger a BadVersion exception. (realm/realm-core#7161, since v10.19.4)

  Compatibility

  • React Native >= v0.71.4
  • Realm Studio v14.0.0.
  • File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

  Internal

  • Upgraded Realm Core from v13.23.4 to v13.24.1. (#6311)

from realm GitHub release notes

Commit messages

Package name: realm

• 542931f [12.5.0] Bump version
• 4533925 Key path filtered notifications in `Object` and `Collection` (#6310)
• 7fec08b Upgrade to Realm Core v13.25.0 (#6325)
• 52ec2e0 Update index.ts to remove cloning a baas fork
• 404e539 Adding a clean command
• 59853f3 Upgraded mocha-remote to v1.8.0 (#6321)
• 6277e34 Upgraded release-to-slack GHA
• 8460c3d Prepare for vNext (#6319)
• 119c6e3 Prepare for 12.4.0 (#6317)

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[codeautopilot]

PR summary

The Pull Request (PR) is an automated update by Snyk to upgrade the realm package from version 12.4.0 to 12.5.0. The realm package is a database library for Node.js, React Native, and Electron applications.

Enhancements in 12.5.0

• Added an optional keyPaths argument to the addListener methods of Collection and Object to specify which property changes should trigger the listener.
• Exceptions during bootstrap application are now surfaced to the user via the sync error handler instead of terminating the program.

Fixes in 12.5.0

• Fixed crashes related to exceptions during bootstrap application and sync session resumption.
• Fixed undefined behavior when adding the same callback function as a listener on a Collection or Object multiple times; it now throws an error.

Compatibility

• Compatible with React Native >= v0.71.4 and Realm Studio v14.0.0.
• Generates Realms with format v23 and can upgrade file formats from v5 or later for non-synced Realms and v10 or later for synced Realms.

Internal Changes

• Upgraded Realm Core from v13.24.1 to v13.25.0.

The PR includes changes to package.json and package-lock.json to update the version of realm.

Suggestion

No suggestions for improvement are provided as the PR is straightforward and follows best practices for dependency updates.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 11.82%

Have feedback or need help?
Discord
Documentation
support@codeautopilot.com

[sourcery-ai]

PR Type: Enhancement

PR Summary: The pull request upgrades the 'realm' package from version 12.4.0 to 12.5.0. This update includes enhancements such as key path filtered notifications for 'Object' and 'Collection', as well as several bug fixes and compatibility improvements.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.

• Sourcery currently only approves 'Typo fix' PRs.

✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.

No details provided.

📝 Complexity: the changes are too large or complex for Sourcery to approve.

• Unsupported files: the diff contains files that Sourcery does not currently support during reviews.

General suggestions:

• Ensure thorough testing is conducted to verify that the new features and bug fixes in 'realm' version 12.5.0 integrate smoothly with the existing codebase.
• Review the release notes and commit messages provided by Snyk to understand the changes and their potential impact on the application.
• Consider the compatibility notes, especially with respect to React Native and Realm Studio versions, to ensure that the application's environment aligns with the requirements of the updated 'realm' package.

Your trial expires on January 15, 2024. Please email tim@sourcery.ai to continue using Sourcery ✨

_{Did you find the review useful? React with a 👍 or 👎 to each comment}