@cesar-richard/git-connector-sdk 4.14.0 → 4.15.0

package/dist/schema.d.ts

@@ -1942,7 +1942,7 @@ export interface components {
             name: string;
             /** @description Raw provider form (`#1f75cb` on GitLab), `null` when the tracker gives none. Same convention as label colours: not normalized here, because `/v1` has always exposed the upstream form and a consumer that normalizes would break if this endpoint alone pre-normalized. */
             color: string | null;
-            /** @description Rank on the tracker's board, `null` when upstream says nothing. Already applied to the array order; exposed so a consumer re-sorting a filtered subset keeps the board order. */
+            /** @description Rank the tracker gives the status, `null` when upstream says nothing. Applied to the array order, BUT measured on a real self-hosted GitLab (2026-10-07) every status came back with `position: 0` — so in practice the order falls back to the status name, alphabetically. Do not read this field as a board order: it is what the provider said, which may well be no ordering at all. A consumer re-sorting a filtered subset should expect to tie on 0 and break the tie the same way. */
             position: number | null;
         };
         ProjectStatusesResponse: {
@@ -1952,7 +1952,7 @@ export interface components {
                 name: string;
                 /** @description Raw provider form (`#1f75cb` on GitLab), `null` when the tracker gives none. Same convention as label colours: not normalized here, because `/v1` has always exposed the upstream form and a consumer that normalizes would break if this endpoint alone pre-normalized. */
                 color: string | null;
-                /** @description Rank on the tracker's board, `null` when upstream says nothing. Already applied to the array order; exposed so a consumer re-sorting a filtered subset keeps the board order. */
+                /** @description Rank the tracker gives the status, `null` when upstream says nothing. Applied to the array order, BUT measured on a real self-hosted GitLab (2026-10-07) every status came back with `position: 0` — so in practice the order falls back to the status name, alphabetically. Do not read this field as a board order: it is what the provider said, which may well be no ordering at all. A consumer re-sorting a filtered subset should expect to tie on 0 and break the tie the same way. */
                 position: number | null;
             }[];
             fetchedAt: string;
@@ -7155,7 +7155,7 @@ export interface operations {
                             name: string;
                             /** @description Raw provider form (`#1f75cb` on GitLab), `null` when the tracker gives none. Same convention as label colours: not normalized here, because `/v1` has always exposed the upstream form and a consumer that normalizes would break if this endpoint alone pre-normalized. */
                             color: string | null;
-                            /** @description Rank on the tracker's board, `null` when upstream says nothing. Already applied to the array order; exposed so a consumer re-sorting a filtered subset keeps the board order. */
+                            /** @description Rank the tracker gives the status, `null` when upstream says nothing. Applied to the array order, BUT measured on a real self-hosted GitLab (2026-10-07) every status came back with `position: 0` — so in practice the order falls back to the status name, alphabetically. Do not read this field as a board order: it is what the provider said, which may well be no ordering at all. A consumer re-sorting a filtered subset should expect to tie on 0 and break the tie the same way. */
                             position: number | null;
                         }[];
                         fetchedAt: string;
@@ -7167,7 +7167,7 @@ export interface operations {
                             name: string;
                             /** @description Raw provider form (`#1f75cb` on GitLab), `null` when the tracker gives none. Same convention as label colours: not normalized here, because `/v1` has always exposed the upstream form and a consumer that normalizes would break if this endpoint alone pre-normalized. */
                             color: string | null;
-                            /** @description Rank on the tracker's board, `null` when upstream says nothing. Already applied to the array order; exposed so a consumer re-sorting a filtered subset keeps the board order. */
+                            /** @description Rank the tracker gives the status, `null` when upstream says nothing. Applied to the array order, BUT measured on a real self-hosted GitLab (2026-10-07) every status came back with `position: 0` — so in practice the order falls back to the status name, alphabetically. Do not read this field as a board order: it is what the provider said, which may well be no ordering at all. A consumer re-sorting a filtered subset should expect to tie on 0 and break the tie the same way. */
                             position: number | null;
                         }[];
                         fetchedAt: string;
@@ -7179,7 +7179,7 @@ export interface operations {
                             name: string;
                             /** @description Raw provider form (`#1f75cb` on GitLab), `null` when the tracker gives none. Same convention as label colours: not normalized here, because `/v1` has always exposed the upstream form and a consumer that normalizes would break if this endpoint alone pre-normalized. */
                             color: string | null;
-                            /** @description Rank on the tracker's board, `null` when upstream says nothing. Already applied to the array order; exposed so a consumer re-sorting a filtered subset keeps the board order. */
+                            /** @description Rank the tracker gives the status, `null` when upstream says nothing. Applied to the array order, BUT measured on a real self-hosted GitLab (2026-10-07) every status came back with `position: 0` — so in practice the order falls back to the status name, alphabetically. Do not read this field as a board order: it is what the provider said, which may well be no ordering at all. A consumer re-sorting a filtered subset should expect to tie on 0 and break the tie the same way. */
                             position: number | null;
                         }[];
                         fetchedAt: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cesar-richard/git-connector-sdk",
-  "version": "4.14.0",
+  "version": "4.15.0",
   "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": {