Response field csr is no longer guaranteed

What changed

Producer-side tools call this non-breaking. For a consumer it is a null dereference on an unknown future date.

Affects csr on tls-certificates-and-hostnames_certificates reachable from 3 operations. Nothing fails at the call; it fails wherever the value is finally used, which is usually somewhere else entirely.

no longer guaranteed present

Who is affected

Code that reads Cloudflare's tls-certificates-and-hostnames_certificates objects, used by 3 Cloudflare operations.

Before and after

Code that breaks

// response.csr may now be absent or null
const csr = response.csr ?? fallback;

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