Driftwatch

Vercel / Vercel REST API /

Breaking

Response field schema 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/global-config.

Who is affected

Code that reads GET /v1/global-config (schema).

Before and after

WhereBeforeAfter
GET /v1/global-config · schemapresentabsent
POST /v1/global-config · syncedToDynamoAtpresentabsent
POST /v1/global-config · transferpresentabsent
GET /v1/global-config/{edgeConfigId} · schemapresentabsent
GET /v1/global-config · purposepresentabsent
GET /v1/global-config · transferpresentabsent
POST /v1/global-config · deletedAtpresentabsent
POST /v1/global-config · purposepresentabsent
POST /v1/global-config · schemapresentabsent
GET /v1/global-config/{edgeConfigId} · deletedAtpresentabsent
GET /v1/global-config/{edgeConfigId} · purposepresentabsent
GET /v1/global-config/{edgeConfigId} · syncedToDynamoAtpresentabsent
GET /v1/global-config/{edgeConfigId} · transferpresentabsent
PUT /v1/global-config/{edgeConfigId} · deletedAtpresentabsent
PUT /v1/global-config/{edgeConfigId} · purposepresentabsent
PUT /v1/global-config/{edgeConfigId} · schemapresentabsent
PUT /v1/global-config/{edgeConfigId} · syncedToDynamoAtpresentabsent
PUT /v1/global-config/{edgeConfigId} · transferpresentabsent

Code that breaks

// response.schema is now undefined
const schema = response.schema;

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