Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade realm from 11.5.2 to 11.6.0 #2733

Merged
merged 2 commits into from
Apr 27, 2023

Conversation

admin-token-bot
Copy link
Contributor

Snyk has created this PR to upgrade realm from 11.5.2 to 11.6.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 22 days ago, on 2023-03-23.
Release notes
Package name: realm
  • 11.6.0 - 2023-03-23

    Enhancements

    • Added configuration option App.baseFilePath which controls where synced Realms and metadata is stored.

    Fixed

    • Fix type error when using realm.create in combination with class base models. (since v11.0.0)

    Compatibility

    • React Native >= v0.71.0
    • Realm Studio v13.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

    • Test
  • 11.5.2 - 2023-03-16

    Fixed

    • Suppress omitting objcMsgsend stubs to ensure backward compatibility with Xcode 13. It can be observed as Undefined symbols for architecture arm64: "_objc_msgSend$allBundles", referenced from: realm::copy_bundled_realm_files() in librealm-js-ios.a(platform.o) when using a React Native app for iOS. (#5511, since v11.5.1)
    • It is not allowed to specify deleteRealmIfMigrationIsNeeded and sync. This can lead to error messages like Schema validation failed due to the following errors. (#5548, v10.12.0)
    • Installation will no longer hang when using Node 19. (#5136, since v10.13.0)
    • Fixed enums which was accidentally exported on the Realm namespace without a backing implementation. (#5493, since v11.0.0)
    • Converting local Realm to synced Realm crashes if an embedded object is null. (#5389, since v10.13.0)
    • Fixed performance degradation on subqueries. (realm/realm-core#6327, since v6.0.0)
    • Fixed crash if secure transport returns an error with a non-zero length. It can be observed as Reading failed: Premature end of input in the log. (realm/realm-core#5435, since v10.0.0)
    • Creating subscriptions with queries having Unicode parameters causes a server error e.g., query from client: "{"Product":"(stringQueryField BEGINSWITH B64\"2KzZhdi52Kpz\" )"}" could not be parsed. (realm/realm-core#6350, since v10.11.0)

    Compatibility

    • React Native >= v0.71.0
    • Atlas App Services.
    • Realm Studio v13.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.4.2 to v13.6.0. (#5495)
    • All exceptions thrown out of Realm Core are now of type Exception.
from realm GitHub release notes
Commit messages
Package name: realm
  • 5196e76 [11.6.0] Bump version
  • 430afad Expose baseFilePath on App configuration (#5572)
  • 22977ea Fix Create Call Signature (#5617)
  • 832fd6a Reenable all tests (#5606)
  • b7245b3 Disable ccache for node builds (#5602)
  • bf629d3 Prepare for vNext (#5567)
  • 46711a5 Prepare for 11.5.2 (#5560)

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

@cbush cbush merged commit ba92962 into master Apr 27, 2023
@cbush cbush deleted the snyk-upgrade-9a089c738a4dd9cb8e87d19b1a793d30 branch April 27, 2023 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants