← All provider guides

Vercel API breaking changes (2026): complete tracker and fixes

vercel 98 breaking / deprecation entries 2026

Vercel ships API and SDK changes continuously. Most are additive — but the ones that are not can silently break integrations that worked yesterday. This page is the complete, continuously regenerated record of every Vercel breaking change and deprecation in the mendapi change database: 98 entries (98 breaking, 0 deprecation), each linked to its upstream source and, where possible, to a concrete fix.

How to read this page

Every entry carries a fixability verdict from the mendapi adjudication pipeline: code-fixable means a mechanical code change repairs the break (73 entries); not code-fixable means the change requires a business decision, credential provisioning, or upstream action that no codemod can produce (25 entries). Entries marked auto-fix pack have a deterministic, gold-tested migration pack that mendapi fix can apply locally.

Am I affected?

Reading a changelog tells you what changed — not whether your code uses the affected surface. The mendapi scanner answers that locally, in about 30 seconds, without any code leaving your machine:

npx mendapi sync
# -> one network call: pulls the change feed into a local database
npx mendapi scan
# -> N findings: file, line, provider, confidence
mendapi deps --match
# -> which of the changes below actually hit your endpoints

See Getting Started for the full workflow and the security model for why zero code upload is the default and only mode.

Complete Vercel breaking change timeline

Automated migration packs for Vercel

mendapi ships 7 deterministic migration packs for Vercel — verified, idempotent codemods you can apply locally with mendapi fix. Full details in the pack catalog.

• vercel-web-analytics-dhe-cipher-suite-removal — Vercel Web Analytics: dheCipherSuite response dimension discontinued (v1.28.9) (upstream reference)
• vercel-project-extended-max-duration-removal — Vercel Projects: enableFunctionsExtendedMaxDuration flag withdrawn from the API surface (v1.28.0) (upstream reference)
• vercel-project-public-source-removal — Vercel Projects: publicSource dropped from all project response schemas (v1.28.0) (upstream reference)
• vercel-store-agent-skill-url-to-agent-skills — Vercel Marketplace stores: product.agentSkillUrl reshaped into the agentSkills array (v1.28.3) (upstream reference)
• vercel-vcr-image-id-or-digest-rename — Vercel VCR: single-image fetch path parameter widened from imageId to imageIdOrDigest (v1.28.9) (upstream reference)
• vercel-integration-resource-edge-config-read-move — Vercel Marketplace: experimentation edge-config fields dropped from the single-resource read (v1.28.9) — reads move to the list endpoint (upstream reference)
• vercel-edge-config-to-global-config-path-rename — Vercel REST API: the /v1/edge-config resource family renamed to /v1/global-config (v1.28.14) (upstream reference)

Measured: when the release notes cry breaking and the spec disagrees

The release notes for @vercel/sdk v1.28.15 flag vercel.user.listUserEvents() and vercel.user.listEventTypes() as Breaking. Diffing the OpenAPI spec behind that release (vercel-oas-v1.28.14-to-v1.28.15) tells a different story: 44 raw diff records and 0 breaking changes — 18 enum-value-added, 17 response-prop-added, 9 request-prop-added. Every record is additive surface growth: new enum values, new response properties, new request properties.

Why the mismatch? The SDK is generated by Speakeasy, and adding a member to a TypeScript union type changes the generated type shape — which the generator dutifully labels breaking at the language-type level. At the wire-contract level nothing an existing caller sends or reads stopped working. A team that trusts the release-note label alone schedules migration work it does not need; a team that ignores it will one day miss a real removal (the v1.28.14 corridor in the timeline above shipped 12 genuine endpoint removals in a patch release). Measuring the spec is how you tell the two apart, per release, in seconds.

Monitoring Vercel going forward

This page is regenerated from the change database, which is fed by release feeds, changelog capture and OpenAPI spec diffing — so it does not depend on Vercel writing a perfect changelog. mendapi monitors 84125 change records across 20 providers; hosted plans watch your repos continuously and open fix PRs when a change lands. See pricing.

Frequently asked questions

Related

• Vercel SDK v1.28 migration — the full migration guide with pack-backed fixes.
• 11 Vercel spec pairs: a real 12-endpoint removal, and the release notes that cried breaking — the long-form methodology report behind this provider's tracked changes.
• API breaking change detection — how upstream breakage is caught before it ships, and why default severity gates stay silent.
• All breaking-change reports — per-change deep dives with migration guides.
• All monitored providers — live change counts.
• Migration pack catalog — every deterministic fix mendapi ships.