[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-gitlab-openapi-2026-06-22-project-id-format-changed-from-int32-to-int64-in-storage":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},"01KVR7V1Z0S04VW67ZDP6RYARF","2026-06-22-project-id-format-changed-from-int32-to-int64-in-storage","Breaking","project_id format changed from int32 to int64 in storage response","The `project_id` field's format was updated from `int32` to `int64` in a response schema. Clients that deserialize this field into a 32-bit integer type will silently overflow or error for project IDs exceeding 2,147,483,647, which is a real concern for large GitLab instances. Any generated SDK code or typed client that mapped `int32` will need to be updated.","2026-06-22T18:00:19.168Z"]