[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-gitlab-openapi-2026-07-10-access-level-fields-changed-from-integer-to-string-in-ai":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},"01KX6FJ0XYFN62JWFE8A1VG99T","2026-07-10-access-level-fields-changed-from-integer-to-string-in-ai","Breaking","Access level fields changed from integer to string in AI settings response","Four fields in the AI\u002FDuo agent settings schema have changed their `type` from `integer` (format `int32`) to `string`: **`minimum_access_level_execute`**, **`minimum_access_level_execute_async`**, **`minimum_access_level_manage`**, and **`minimum_access_level_enable_on_projects`**. Clients that parse these fields as numbers (e.g. `30` for developer, `40` for maintainer) will now receive role-name strings like `\"developer\"` or `\"maintainer\"` instead, breaking any numeric comparison or deserialization logic.","2026-07-10T17:00:15.678Z"]