Vercel: purchaseType can now return "14cpu-28gb"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects config.resourceConfig.buildMachine.purchaseType on PATCH /v12/deployments/{id}/cancel.

New value: 14cpu-28gb.

can now return "14cpu-28gb"

Who is affected

Code that reads PATCH /v12/deployments/{id}/cancel (config.resourceConfig.buildMachine.purchaseType).

Before and after

Where	Before	After
PATCH /v12/deployments/{id}/cancel · config.resourceConfig.buildMachine.purchaseType	"basic", "enhanced", "standard", "turbo", null	"14cpu-28gb", "basic", "enhanced", "standard", "turbo", null
POST /v13/deployments · config.resourceConfig.buildMachine.purchaseType	"basic", "enhanced", "standard", "turbo", null	"14cpu-28gb", "basic", "enhanced", "standard", "turbo", null
GET /v13/deployments/{idOrUrl} · config.resourceConfig.buildMachine.purchaseType	"basic", "enhanced", "standard", "turbo", null	"14cpu-28gb", "basic", "enhanced", "standard", "turbo", null

Code that breaks

switch (response.config.resourceConfig.buildMachine.purchaseType) {
  // existing branches …
  // no branch for "14cpu-28gb"
  default:
    throw new Error("unexpected purchaseType");
}

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