Driftwatch

Vercel / Vercel REST API /

Breaking

Response field minSampleSize 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[].rollingRelease.gate.checks[].minSampleSize).

Before and after

WhereBeforeAfter
GET /v1/microfrontends/groups/{groupId}/projects · projects[].rollingRelease.gate.checks[].minSampleSizepresentabsent
POST /v11/projects · rollingRelease.gate.checks[].minSampleSizepresentabsent
GET /v9/projects/{idOrName} · rollingRelease.gate.checks[].minSampleSizepresentabsent
POST /v1/projects/{idOrName}/avatar · rollingRelease.gate.checks[].minSampleSizepresentabsent
GET /v1/projects/{idOrName}/rolling-release/config · rollingRelease.gate.checks[].minSampleSizepresentabsent
PATCH /v1/projects/{projectId}/microfrontends · rollingRelease.gate.checks[].minSampleSizepresentabsent
GET /v10/projects · rollingRelease.gate.checks[].minSampleSizepresentabsent
GET /v10/projects · projects[].rollingRelease.gate.checks[].minSampleSizepresentabsent
PATCH /v9/projects/{idOrName} · rollingRelease.gate.checks[].minSampleSizepresentabsent

Code that breaks

// response.projects[0].rollingRelease.gate.checks[0].minSampleSize is now undefined
const minSampleSize = response.projects[0].rollingRelease.gate.checks[0].minSampleSize;

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