[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-22-remove-publicdeployments-field-from-deployment-policy":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},"01KS837TDDB76ZR6TEAQTQ9EJG","2026-05-22-remove-publicdeployments-field-from-deployment-policy","Breaking","Remove publicDeployments field from deployment policy schemas","The **`publicDeployments`** field (with `enabled` and `allowPublicDeployments` sub-properties) has been removed from all deployment policy schemas — including project-level (`deploymentPolicy`) and team-level (`TeamDeploymentPolicy`) shapes, across both request and response contexts. Clients that read or write `publicDeployments` to control whether deployments can have their source\u002Flogs exposed publicly will no longer find this field documented and may receive unexpected behaviour if they relied on it.","2026-05-22T15:00:39.981Z"]