@cesar-richard/git-connector-sdk 4.18.0 → 4.19.1

package/dist/schema.d.ts

@@ -129,6 +129,7 @@ export interface paths {
         delete?: never;
         options?: never;
         head?: never;
+        /** @description Partial upsert of a tracker's delivery/opened label and native-status sets. Judged on the RESULT of the partial upsert, not on the patch. One combination is rejected with 400: a GITHUB tracker declaring delivering statuses and NO delivery label — the Project v2 status CHRONOLOGY has no reader, so nothing would be left to classify a delivery and the tracker's CRA would be silently empty. GitHub + statuses + labels is accepted (the label stage governs, the status stage contributes nothing it can read), `openedStatuses` is unaffected, and clearing `deliveryStatuses` is always accepted. GitLab accepts status-only rules — that is a supported, label-free delivery process. */
         patch: operations["patchV1ProjectsBySourceByProjectKeyDelivery-rules"];
         trace?: never;
     };
@@ -6615,6 +6616,22 @@ export interface operations {
                     };
                 };
             };
+            400: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": {
+                        error: string;
+                    };
+                    "multipart/form-data": {
+                        error: string;
+                    };
+                    "text/plain": {
+                        error: string;
+                    };
+                };
+            };
         };
     };
     "getV1ApplicationsBySlugDelivery-rules": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cesar-richard/git-connector-sdk",
-  "version": "4.18.0",
+  "version": "4.19.1",
   "description": "TypeScript SDK for the git-connector v1 API (work items + iterations aggregated from GitHub/GitLab). Version published on npm tracks server releases.",
   "license": "MIT",
   "repository": {