[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-gitlab-openapi-2026-07-03-new-required-field-uuid-added-to-ci-jobrequest-runnerinfo":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},"01KWM4GDWTYASG77AFXFB4MTY1","2026-07-03-new-required-field-uuid-added-to-ci-jobrequest-runnerinfo","Breaking","New required field `uuid` added to CI JobRequest RunnerInfo response","The **`uuid`** field (type `string`) has been added to `API_Entities_Ci_JobRequest_RunnerInfo` and marked as **required**. Any client or code generator that validates response payloads against this schema and previously operated without `uuid` will now see validation failures, making this a potentially breaking change for strict schema consumers. Clients that only read the fields they care about and ignore extras are unaffected.","2026-07-03T14:00:49.306Z"]