What changed
Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.
Affects result[].type on GET /accounts/{account_id}/pipelines/v1/sinks.
New value: basin_catalog.
can now return "basin_catalog"
Who is affected
Code that reads GET /accounts/{account_id}/pipelines/v1/sinks (result[].type).
Before and after
| Where | Before | After |
|---|---|---|
| GET /accounts/{account_id}/pipelines/v1/sinks · result[].type | "r2", "r2_data_catalog" | "basin_catalog", "r2", "r2_data_catalog" |
| POST /accounts/{account_id}/pipelines/v1/sinks · result.type | "r2", "r2_data_catalog" | "basin_catalog", "r2", "r2_data_catalog" |
| GET /accounts/{account_id}/pipelines/v1/sinks/{sink_id} · result.type | "r2", "r2_data_catalog" | "basin_catalog", "r2", "r2_data_catalog" |
Code that breaks
switch (response.result[0].type) {
// existing branches …
// no branch for "basin_catalog"
default:
throw new Error("unexpected type");
}Based on Cloudflare’s published API specification. How severity is decided.