OpenAI: role is no longer accepted

OpenAI's published API specification no longer accepts the `role` field on `DecisionInputMessage`, which is reachable from one OpenAI operation, according to an API-change tracker. The field was previously present and is now absent; the tracker warns that requests sending `role` are typically ignored rather than rejected, so the call succeeds while behaving subtly differently. The change affects code that sends `DecisionInputMessage` objects to that single operation, and the tracker advises developers to grep for the field because nothing else will flag it.

What changed Usually ignored rather than rejected, so the call succeeds and does something subtly different. Affects role on DecisionInputMessage reachable from 1 operation. Grep for it: nothing else will tell you. Who is affected Code that sends OpenAI's DecisionInputMessage objects, used by 1 OpenAI operation. Before and after | Where | Before | After | |---|---|---| | DecisionInputMessage.role | present | absent | Code that breaks await client.post "/…", { // role is now ignored, not rejected role: value, } ; Based on OpenAI’s published API specification. How severity is decided https://driftwatch.et/method .