← All breaking-change reports

Vercel API breaking change: response-prop-removed on POST /v1/storage/stores/integration/direct

vercel · breaking · source: OpenAPI spec diff

What changed

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

response-prop-removed: POST /v1/storage/stores/integration/direct -> 200 store.product.agentSkillUrl

Who is affected

The singular agentSkillUrl string was reshaped into the plural agentSkills array in the same release, with an identical description on the same product object.

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

npx mendapi sync  # the one network call: fetch the change feed
npx mendapi scan --repo .  # local scan, nothing leaves your machine

How to fix it

mendapi ships a deterministic migration pack for this change (vercel-store-agent-skill-url-to-agent-skills). Preview the patch locally (dry-run is the default; nothing is modified without --apply):

npx mendapi fix --repo . --migration vercel-store-agent-skill-url-to-agent-skills

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

What the migration does:

The singular agentSkillUrl string was reshaped into the plural agentSkills array in the same release, with an identical description on the same product object. Consumers reading the single URL should read the first entry of the array (or iterate all entries if they can consume multiple guides). The mechanical migration is a field rename plus an index or iteration: product.agentSkillUrl becomes product.agentSkills?.[0] for single-URL consumers.

Before:

const skillUrl = store.product.agentSkillUrl;

After:

const skillUrl = store.product.agentSkills?.[0];
// or iterate store.product.agentSkills for all guide URLs

Replacement data source: store.product.agentSkills (array of skill/guide URLs) introduced in v1.28.3 on the same response object.

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

Related

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