Apply scheduled running result

Outputs/Apollo iOS.json

@@ -911,6 +911,18 @@
     "url" : "https://github.com/apollographql/apollo-ios/releases/tag/1.9.2",
     "version" : "1.9.2"
   },
+  {
+    "body" : "### New\r\n- **Experimental support for the `@defer` directive:** You can now use the `@defer` directive in your operations and code generation will generate models that support asynchronously receiving the deferred selection sets. There is a helpful property wrapper with a projected value to determine the state of the deferred selection set, and support for cache reads and writes. This feature is enabled by default but is considered [experimental](https://www.apollographql.com/docs/resources/product-launch-stages/#experimental-features). Please refer to the [documentation](https://www.apollographql.com/docs/ios/fetching/defer/) for further details.\r\n- **Add `debugDescription` to `SelectionSet` ([#3374](https://github.com/apollographql/apollo-ios/issues/3374)):** This adds the ability to easily print code generated models to the Xcode debugger console. See PR [#412](https://github.com/apollographql/apollo-ios-dev/pull/412). _Thanks to [@raymondk-nf](https://github.com/raymondk-nf) for raising the issue._\r\n- **Xcode 16 editor config files ([#3404](https://github.com/apollographql/apollo-ios/issues/3404)):** Xcode 16 introduced support for `.editorconfig` files that represent settings like spaces vs. tabs, how many spaces per tab, etc. We've added a `.editorconfig` file with the projects preferred settings, so that the editor will use them automatically. See PR [#419](https://github.com/apollographql/apollo-ios-dev/pull/419). _Thanks to [@TizianoCoroneo](https://github.com/TizianoCoroneo) for raising the issue._\r\n\r\n### Fixed\r\n- **Local cache mutation build error in Swift 6 ([#3398](https://github.com/apollographql/apollo-ios/issues/3398)):** Mutating a property of a fragment annotated with the `@apollo_client_ios_localCacheMutation` directive caused a compile time error in Xcode 16 with Swift 6. See PR [#417](https://github.com/apollographql/apollo-ios-dev/pull/417). _Thanks to [@martin-muller](https://github.com/martin-muller) for raising the issue._",
+    "createdAt" : "2024-07-20T06:48:54+09:00",
+    "fetchedFromAPIAt" : "2024-07-20T09:59:18+09:00",
+    "id" : "RE_kwDOA9NCTc4J6ahq",
+    "owner" : "apollographql",
+    "publishedAt" : "2024-07-20T07:00:51+09:00",
+    "repository" : "apollo-ios",
+    "title" : "1.14.0",
+    "url" : "https://github.com/apollographql/apollo-ios/releases/tag/1.14.0",
+    "version" : "1.14.0"
+  },
   {
     "body" : "### New\r\n\r\n- **Added support for visionOS ([#3320](https://github.com/apollographql/apollo-ios/issues/3320)):** All the dependecies that Apollo iOS requires have been updated to add support for visionOS, so we can now add official support for visionOS too. See PR [#333](https://github.com/apollographql/apollo-ios-dev/pull/333).\r\n\r\n### Improvement\r\n\r\n- **Add Sendable conformance to some basic SchemaTypes:** This adds `Sendable` conformance to the some of the generated schema types. This does not mean that all of the generated code is safe to use yet with complete concurrency checking of Swift 5.10 but it gets us closer to that goal. See PR [#322](https://github.com/apollographql/apollo-ios-dev/pull/322). _Thanks to [@bdbergeron](https://github.com/bdbergeron) for the contributon._",
     "createdAt" : "2024-04-16T05:31:27+09:00",

Outputs/Realm.json

@@ -923,6 +923,18 @@
     "url" : "https://github.com/realm/realm-swift/releases/tag/v10.48.1",
     "version" : "v10.48.1"
   },
+  {
+    "body" : "### Enhancements\n\n* Server-side role and permissions changes no longer require a client reset to\n  update the local Realm. ([Core #7440](https://github.com/realm/realm-core/pull/7440))\n\n### Fixed\n\n* Deleting an object with a `List<AnyRealmValue` proeprty which linked to an\n  object which had been deleted by another sync client would switch to the\n  incorrect cascade mode and perform a cascading delete. This meant that if any\n  subsequent properties in the object linked to another top-level object and\n  that was the *only* link to that object, the target object would also be\n  recursively deleted as if it was an embedded object.\n  ([Core #7828](https://github.com/realm/realm-core/issues/7828), since v10.51.0).\n* Fix the assertion failure `array_backlink.cpp:112: Assertion failed:\n  int64_t(value >> 1) == key.value` when removing links to an object (either by\n  reassigning the link or by deleting the object). This could happen if the link\n  came from a collection inside a `AnyRealmValue`, any `Map`, or a\n  `List<AnyRealmValue>`, and there were more than 256 objects of the type which\n  contained the link.\n ([Core #7594](https://github.com/realm/realm-core/issues/7594), since v10.8.0)\n* Fix the assertion failure `array.cpp:319: Array::move() Assertion failed:\n  begin <= end [2, 1]` when deleting objects containing collections nested\n  inside a `AnyRealmValue` when this caused bptree leaves to be merged.\n  ()[Core #7839](https://github.com/realm/realm-core/issues/7839), since v10.51.0).\n* `SyncSession.wait(for .upload)` was inconsistent in how it handled commits\n  which do no produce any changesets to upload (such as modifying flexible sync\n  subscriptions). Previously if all unuploaded commits had empty changesets and\n  the session had never completed a download it would wait for download\n  completion, and otherwise it would complete immediate. It now always\n  completes immediately. ([Core #7796](https://github.com/realm/realm-core/pull/7796)).\n* The sync client could hit an assertion failure if a session is resumed while\n  the session is being suspended. ([Core #7860](https://github.com/realm/realm-core/issues/7860), since v10.27.0)\n* If a sync session was interrupted by a disconnect or restart while downloading\n  a bootstrap (a set of downloads caused by adding or changing a query\n  subscription), stale data from the previous bootstrap could be included when\n  the session reconnected and completed downloading the bootstrap. This could\n  lead to objects stored in the database that do not match the actual state of\n  the server and potentially leading to compensating writes.\n  ([Core #7827](https://github.com/realm/realm-core/issues/7827), since v10.27.0)\n* Fixed unnecessary server roundtrips when there was no download to acknowledge\n  ([Core #2129](https://jira.mongodb.org/browse/RCORE-2129), since v10.51.0).\n\n### Compatibility\n\n* Realm Studio: 15.0.0 or later.\n* APIs are backwards compatible with all previous releases in the 10.x.y series.\n* Carthage release for Swift is built with Xcode 15.4.0.\n* CocoaPods: 1.10 or later.\n* Xcode: 15.1.0-16 beta 3.\n\n### Internal\n\n* Upgraded realm-core from v14.10.2 to 14.11.0",
+    "createdAt" : "2024-07-20T04:28:18+09:00",
+    "fetchedFromAPIAt" : "2024-07-20T09:59:18+09:00",
+    "id" : "RE_kwDOAD24W84J6Wul",
+    "owner" : "realm",
+    "publishedAt" : "2024-07-20T04:29:25+09:00",
+    "repository" : "realm-swift",
+    "title" : "v10.52.2",
+    "url" : "https://github.com/realm/realm-swift/releases/tag/v10.52.2",
+    "version" : "v10.52.2"
+  },
   {
     "body" : "### Enhancements\n\n* The default base url in `AppConfiguration` has been updated to point to `services.cloud.mongodb.com`. See https://www.mongodb.com/docs/atlas/app-services/domain-migration/ for more information. ([#8512](https://github.com/realm/realm-swift/issues/8512))\n\n### Fixed\n\n* Fixed a crash that would occur when an http error 401 or 403 is returned upon\n  opening a watch stream for a MongoDB collection. ([#8519](https://github.com/realm/realm-swift/issues/8519))\n* Fix an assertion failure \"m_lock_info && m_lock_info->m_file.get_path() == m_filename\" that appears to be related to opening a Realm while the file is in the process of being closed on another thread. ([#8507](https://github.com/realm/realm-swift/issues/8507))\n* Fixed diverging history due to a bug in the replication code when setting default null values (embedded objects included). ([Core #7536](https://github.com/realm/realm-core/issues/7536))\n* Null pointer exception may be triggered when logging out and async commits callbacks not executed. ([Core #7434](https://github.com/realm/realm-core/issues/7434))\n* `AppConfiguration.baseUrl` will now return the default value of the url when not set rather than `nil`. ([#8512](https://github.com/realm/realm-swift/issues/8512))\n* Added privacy manifest to Core's Swift package ([Swift #8535](https://github.com/realm/realm-swift/issues/8535))\n* Fixed crash when integrating removal of already removed dictionary key ([Core #7488](https://github.com/realm/realm-core/issues/7488), since v10.0.0)\n\n### Compatibility\n\n* Realm Studio: 15.0.0 or later.\n* APIs are backwards compatible with all previous releases in the 10.x.y series.\n* Carthage release for Swift is built with Xcode 15.3.0.\n* CocoaPods: 1.10 or later.\n* Xcode: 14.2-15.3.0.\n\n### Internal\n\n* Upgraded realm-core from 14.4.1 to 14.5.2",
     "createdAt" : "2024-04-18T04:42:04+09:00",