← All breaking-change reports

Vercel API breaking change: response-prop-became-nullable on POST /v1/projects/{idOrName}/avatar

vercel · breaking · upstream source

What changed

According to the OpenAPI spec diff (vercel/vercel-oas-v1.27.0-to-v1.28.0), the following surface changed:

response-prop-became-nullable: POST /v1/projects/{idOrName}/avatar -> 200 avatar

Who is affected

The avatar field on project responses became nullable.

To find out whether your repo is hit — file and line number, no code leaving your machine:

npx mendapi scan --repo .

How to fix it

Migration path:

The avatar field on project responses became nullable. Code that calls string methods on it, interpolates it into URLs, or passes it to non-null-tolerant sinks can now throw or render "null". The mechanical fix is to add a null guard at each read site: optional chaining, a nullish-coalescing fallback, or an early return when avatar is null. No data was removed; only the absent-avatar case is now represented as null instead of being guaranteed a string.

Before:

const url = `https://vercel.com/api/www/avatar/${project.avatar}`;

After:

const url = project.avatar ? `https://vercel.com/api/www/avatar/${project.avatar}` : DEFAULT_AVATAR_URL;

With your own LLM key configured (BYO compute — mendapi never proxies your credentials), npx mendapi llmfix turns this guide into a reviewable draft patch for your repo.

Detected and tracked by mendapi — Dependabot for every API you depend on. Scans run locally; your code never leaves your machine.

Related

Pre-release. Change data is recorded from upstream provider releases, changelogs and OpenAPI spec diffs; every article links its source.