Driftwatch

Vercel / Vercel REST API /

Breaking

Response field abuse removed

What changed

Reads of this field return undefined, and the failure surfaces wherever that value is used rather than at the call.

Affects GET /v1/microfrontends/groups/{groupId}/projects.

Who is affected

Code that reads GET /v1/microfrontends/groups/{groupId}/projects (projects[].abuse).

Before and after

WhereBeforeAfter
GET /v1/microfrontends/groups/{groupId}/projects · projects[].abusepresentabsent
POST /v1/projects/{idOrName}/avatar · abusepresentabsent
PATCH /v1/projects/{projectId}/microfrontends · abusepresentabsent
GET /v10/projects · projects[].abusepresentabsent
GET /v10/projects · abusepresentabsent
POST /v11/projects · abusepresentabsent
GET /v9/projects/{idOrName} · abusepresentabsent
PATCH /v9/projects/{idOrName} · abusepresentabsent

Code that breaks

// response.projects[0].abuse is now undefined
const abuse = response.projects[0].abuse;

Based on Vercel’s published API specification. How severity is decided.