Update gh-pages to output generated at 13fc1f9

data/schema-changes.json

@@ -1,7 +1,17 @@
 [
+  {
+    "diff": "field_new",
+    "type": "CheckoutSettings",
+    "field": "automaticallyCompleteFullyPaidCheckouts"
+  },
+  {
+    "diff": "field_new",
+    "type": "CheckoutSettingsInput",
+    "field": "automaticallyCompleteFullyPaidCheckouts"
+  },
   {
     "diff": "enum_value_new",
-    "enum": "TransactionEventReportErrorCode",
-    "value": "REQUIRED"
+    "enum": "OrderEventsEnum",
+    "value": "PLACED_AUTOMATICALLY_FROM_PAID_CHECKOUT"
   }
 ]

data/schema-previous.json

@@ -11261,6 +11261,13 @@
     "deprecated": null,
     "message": null,
     "fields": {
+      "automaticallyCompleteFullyPaidCheckouts": {
+        "type": "Boolean!",
+        "description": "Default `false`. Determines if the paid checkouts should be automatically completed. This setting applies only to checkouts where payment was processed through transactions.When enabled, the checkout will be automatically completed once the checkout `charge_status` reaches `FULL`. This occurs when the total sum of charged and authorized transaction amounts equals or exceeds the checkout's total amount.\n\nAdded in Saleor 3.20.",
+        "deprecated": null,
+        "message": null,
+        "arguments": {}
+      },
       "useLegacyErrorFlow": {
         "type": "Boolean!",
         "description": "Default `true`. Determines if the checkout mutations should use legacy error flow. In legacy flow, all mutations can raise an exception unrelated to the requested action - (e.g. out-of-stock exception when updating checkoutShippingAddress.) If `false`, the errors will be aggregated in `checkout.problems` field. Some of the `problems` can block the finalizing checkout process. The legacy flow will be removed in Saleor 4.0. The flow with `checkout.problems` will be the default one.\n\nAdded in Saleor 3.15.This field will be removed in Saleor 4.0.",
@@ -11276,6 +11283,13 @@
     "deprecated": null,
     "message": null,
     "fields": {
+      "automaticallyCompleteFullyPaidCheckouts": {
+        "type": "Boolean",
+        "description": "Default `false`. Determines if the paid checkouts should be automatically completed. This setting applies only to checkouts where payment was processed through transactions.When enabled, the checkout will be automatically completed once the checkout `charge_status` reaches `FULL`. This occurs when the total sum of charged and authorized transaction amounts equals or exceeds the checkout's total amount.\n\nAdded in Saleor 3.20.",
+        "deprecated": null,
+        "message": null,
+        "default": null
+      },
       "useLegacyErrorFlow": {
         "type": "Boolean",
         "description": "Default `true`. Determines if the checkout mutations should use legacy error flow. In legacy flow, all mutations can raise an exception unrelated to the requested action - (e.g. out-of-stock exception when updating checkoutShippingAddress.) If `false`, the errors will be aggregated in `checkout.problems` field. Some of the `problems` can block the finalizing checkout process. The legacy flow will be removed in Saleor 4.0. The flow with `checkout.problems` will be the default one. \n\nAdded in Saleor 3.15.\n\nDEPRECATED: this field will be removed in Saleor 4.0.",
@@ -38314,6 +38328,11 @@
         "deprecated": null,
         "message": null
       },
+      "PLACED_AUTOMATICALLY_FROM_PAID_CHECKOUT": {
+        "description": null,
+        "deprecated": null,
+        "message": null
+      },
       "PLACED_FROM_DRAFT": {
         "description": null,
         "deprecated": null,

index.html

@@ -12,7 +12,7 @@
   <div class="container py-3">
     <div class="border-bottom py-3 mb-3">
       <h1>Saleor Deprecations Report</h1>
-      <p class="m-0">Generated on 2024-10-07 14:01:06</p>
+      <p class="m-0">Generated on 2024-10-08 14:00:55</p>
     </div>
     <div class="py-3 my-3">
       <h2 class="fs-4 mb-3">Summary</h2>