[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-gitlab-openapi-2026-06-09-permission-scope-renamed-update-sast-vulnerability":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},"01KTNPAZC159E6PB14TWSQ8T04","2026-06-09-permission-scope-renamed-update-sast-vulnerability","Breaking","Permission scope renamed: update_sast_vulnerability_resolution_setting → update_sec_ai_workflow_settings","The permission\u002Fscope field **`update_sast_vulnerability_resolution_setting`** has been renamed to **`update_sec_ai_workflow_settings`** in both the response schema properties and the enum list. Any client or integration that checks for, passes, or stores the old scope name `update_sast_vulnerability_resolution_setting` will break — the old value no longer appears in the spec.","2026-06-09T08:00:15.745Z"]