[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-gitlab-openapi-2026-06-24-multiple-response-fields-widened-from-int32-to-int64-agent":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"gitlab-openapi","GitLab API","gitlab","openapi-yaml","rest","https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fgitlab\u002F-\u002Fraw\u002Fmaster\u002Fdoc\u002Fapi\u002Fopenapi\u002Fopenapi_v2.yaml",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KVVS4N9DH2DH7DZRZ4V9G0K3","2026-06-24-multiple-response-fields-widened-from-int32-to-int64-agent","Breaking","Multiple response fields widened from int32 to int64; Agent\u002FCluster field types corrected","Several categories of changes are present in this diff:\n\n- **`int32` → `int64`** on `id`, `project_id`, and `pipeline_id` fields across many CI\u002FCD, pipeline, environment, runner, and deployment response schemas. Strictly speaking this is a widening (larger value range), but strongly-typed clients that generated code from `int32` may overflow or need recompilation.\n- **`type: string` → `type: integer` (int64)** for `id`, `agent_id`, and `created_by_user_id` in `API_Entities_Clusters_AgentTokenBasic`, `API_Entities_Clusters_AgentToken`, `API_Entities_Clusters_AgentTokenWithToken`, and `API_Entities_Clusters_Agent`. Any client that parsed these fields as strings will break.\n- **`is_receptive`** in `API_Entities_Clusters_Agent` changed from `type: string` to `type: boolean` — string-parsing clients will break.\n- **`created_at` \u002F `last_used_at`** in Agent\u002FToken schemas gained `format: date-time` (additive but narrows expected format).\n- **`API_Entities_DiscoveredClusters`** fields `groups` and `projects` changed from `type: string` to `type: object` — clients treating these as strings will break.","2026-06-24T03:00:22.957Z"]