[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-29-remove-delegated-protection-fields-acl-actions-and-audit":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"vercel-changelog","Vercel API","vercel","openapi-json","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KST7ER9KJKNVT35EQ77KK4NN","2026-05-29-remove-delegated-protection-fields-acl-actions-and-audit","Breaking","Remove delegated protection fields, ACL actions, and audit log events","Several \"delegated protection\" API surface areas have been removed from the spec:\n- **`delegatedProtection`** response field removed from project objects across multiple response schemas.\n- **`delegatedProtectionClient`** and **`projectDelegatedProtection`** ACL action arrays removed from permission\u002Frole schemas.\n- Audit log event types **`project-delegated-protection-enabled`**, **`project-delegated-protection-updated`**, and **`project-delegated-protection-disabled`** removed from event type enums, along with their associated payload schemas (`clientId`, `projectId`, `projectName`, `next`\u002F`previous` update objects).\n- `updatedAt` field reordered (not removed) in a git-related schema.\n\nClients reading `delegatedProtection` from project responses, checking `delegatedProtectionClient`\u002F`projectDelegatedProtection` permissions, or filtering\u002Fhandling delegated-protection audit events will see these fields\u002Fvalues disappear.","2026-05-29T16:00:41.267Z"]