[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-18-deployment-source-enum-api-removed-replaced-with-rest-api":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},"01KRYHNZ9MJNSQ424G5YE4NM9A","2026-05-18-deployment-source-enum-api-removed-replaced-with-rest-api","Breaking","Deployment source enum: 'api' removed, replaced with 'rest-api', 'deploy-hook', 'integration'","The `\"api\"` enum value in the `sources` field (used to filter\u002Fidentify deployment trigger mechanisms) has been removed and replaced with three more specific values: `\"rest-api\"`, `\"deploy-hook\"`, and `\"integration\"`. Any client that sends or checks for `\"api\"` as a deployment source — e.g. in deployment protection policies or filtering — will break, since `\"api\"` is no longer a valid enum member. The new values allow finer-grained control: `\"rest-api\"` covers direct REST API uploads, `\"deploy-hook\"` covers deploy-hook URL triggers, and `\"integration\"` covers OAuth2\u002Fintegration-actor deployments.","2026-05-18T22:00:39.476Z"]