Release v10.15.0

realm · Sep 10, 2021 · c619512 · c619512
1 parent 5bf15af
commit c619512
Show file tree

Hide file tree

Showing 4 changed files with 17 additions and 12 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,7 +1,9 @@
-x.y.z Release notes (yyyy-MM-dd)
+10.15.0 Release notes (2021-09-10)
 =============================================================
+
 ### Enhancements
-* Add `async` `Realm.asyncOpen` and `App.login` methods.
+
+* Add `async` versions of the  `Realm.asyncOpen` and `App.login` methods.
 * ThreadSafeReference no longer pins the source transaction version for
   anything other than a Results created by filtering a collection. This means
   that holding on to thread-safe references to other things (such as Objects)
@@ -14,27 +16,30 @@ x.y.z Release notes (yyyy-MM-dd)
   ([Core #4839](https://github.com/realm/realm-core/pull/4839))
 
 ### Fixed
-* Adding an unmanaged object to a Realm that was declared with `@StateRealmObject` would throw
-  the exception `"Cannot add an object with observers to a Realm"`.
-* The `RealmCollectionChange` docs refered to indicies in modifications as the 'new' collection. This is
-  incorrect and the docs now state that modifications refer to the previous version of the collection. ([Cocoa #7390](https://github.com/realm/realm-cocoa/issues/7390))
+
+* Adding an unmanaged object to a Realm that was declared with
+  `@StateRealmObject` would throw the exception `"Cannot add an object with
+  observers to a Realm"`.
+* The `RealmCollectionChange` docs refered to indicies in modifications as the
+  'new' collection. This is incorrect and the docs now state that modifications
+  refer to the previous version of the collection. ([Cocoa #7390](https://github.com/realm/realm-cocoa/issues/7390))
 * Fix crash in `RLMSyncConfiguration.initWithUser` error mapping when a user is disabled/deleted from MongoDB Realm dashboard.
   ([Cocoa #7399](https://github.com/realm/realm-cocoa/issues/7399), since v10.0.0)
 * If the application crashed at the wrong point when logging a user in, the
   next run of the application could hit the assertion failure "m_state ==
   SyncUser::State::LoggedIn" when a synchronized Realm is opened with that
   user. ([Core #4875](https://github.com/realm/realm-core/issues/4875), since v10.0.0)
 
-<!-- ### Breaking Changes - ONLY INCLUDE FOR NEW MAJOR version -->
-
 ### Compatibility
+
 * Realm Studio: 11.0.0 or later.
 * APIs are backwards compatible with all previous releases in the 10.x.y series.
 * Carthage release for Swift is built with Xcode 12.5.1.
 * CocoaPods: 1.10 or later.
 * Xcode: 12.2-13.0 beta 5.
 
 ### Internal
+
 * Upgraded realm-core from 11.3.1 to 11.4.1
 
 10.14.0 Release notes (2021-09-03)

diff --git a/Package.swift b/Package.swift
@@ -4,7 +4,7 @@ import PackageDescription
 import Foundation
 
 let coreVersionStr = "11.4.1"
-let cocoaVersionStr = "10.14.0"
+let cocoaVersionStr = "10.15.0"
 
 let coreVersionPieces = coreVersionStr.split(separator: ".")
 let coreVersionExtra = coreVersionPieces[2].split(separator: "-")

diff --git a/Realm/Realm-Info.plist b/Realm/Realm-Info.plist
@@ -17,11 +17,11 @@
 	<key>CFBundlePackageType</key>
 	<string>FMWK</string>
 	<key>CFBundleShortVersionString</key>
-	<string>10.14.0</string>
+	<string>10.15.0</string>
 	<key>CFBundleSignature</key>
 	<string>????</string>
 	<key>CFBundleVersion</key>
-	<string>10.14.0</string>
+	<string>10.15.0</string>
 	<key>NSHumanReadableCopyright</key>
 	<string>Copyright © 2014-2021 Realm. All rights reserved.</string>
 	<key>NSPrincipalClass</key>

diff --git a/dependencies.list b/dependencies.list
@@ -1,3 +1,3 @@
-VERSION=10.14.0
+VERSION=10.15.0
 REALM_CORE_VERSION=11.4.1
 STITCH_VERSION=45504b796f90c58ab56a3d4c34f1031f23d7e199