← All breaking-change reports

Vercel API breaking change: operation-removed on GET /v1/vcr/repository/{idOrName}/images/{imageId}

vercel · breaking · upstream source

What changed

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

operation-removed: GET /v1/vcr/repository/{idOrName}/images/{imageId}

Who is affected

The single-image fetch operation was re-declared with a widened path parameter that accepts either an image id or a digest.

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

mendapi ships a deterministic migration pack for this change (vercel-vcr-image-id-or-digest-rename). Preview the patch locally (dry-run is the default; nothing is modified without --apply):

npx mendapi fix --repo . --migration vercel-vcr-image-id-or-digest-rename

The pack is idempotent, gold-regression tested, and safe on partially migrated code.

What the migration does:

The single-image fetch operation was re-declared with a widened path parameter that accepts either an image id or a digest. Path parameter names never appear on the wire, and existing image ids remain valid inputs, so raw REST callers keep working unchanged - the mend is confirming the call site and optionally adopting digest lookups. SDK-generated clients are the real breakage surface: the generated method parameter renames from imageId to imageIdOrDigest, so typed call sites must rename the argument.

Before:

const img = await vercel.vcr.getImage({ idOrName: repo, imageId });

After:

const img = await vercel.vcr.getImage({ idOrName: repo, imageIdOrDigest: imageId }); // ids remain valid; digests now also accepted

Replacement data source: GET /v1/vcr/repository/{idOrName}/images/{imageIdOrDigest} - widened successor operation accepting an image id or digest.

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.