Response field bytes 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 bytes on OpenAIFile reachable from 6 operations. Nothing fails at the call; it fails wherever the value is finally used, which is usually somewhere else entirely.

can now be null

Who is affected

Code that reads OpenAI's OpenAIFile objects, used by 6 OpenAI operations.

Before and after

Code that breaks

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

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