Structured Output Schema Validation Changed Without Notice — Previously Valid Schemas Now Rejected

We ran into a serious issue this morning involving the structured‑output JSON Schema validator used by the Responses API. A schema that had been valid—and in production—suddenly began failing validation with no code changes on our side.

What Happened
Our application uses the json_schema structured‑output mode.

The schema had been accepted for weeks and was generating correct structured output.

At some point in the evening of 6/18/2026 EDT, the same schema began failing validation.

No changes were made to:

our schema

our request envelope

our model version

our deployment environment

The only plausible change was on the server‑side validator.

The Breaking Change
The validator appears to have tightened or altered its interpretation of JSON Schema in a way that is not backward‑compatible.

Specifically, we observed:

A schema that previously validated now fails unless rewritten in a more restrictive or differently structured form.

Fields/constructs that were previously allowed are now rejected.

The failure is reproducible and tied directly to the schema, not to the request envelope or runtime environment.

This effectively turned a previously valid production schema into an invalid one overnight.

Impact
This caused:

Production breakage

Time‑consuming debugging to confirm the issue was not on our side

A need to rewrite the schema to satisfy new, undocumented validator behavior

For teams relying on structured output for deterministic workflows, this kind of unannounced change is extremely disruptive.

What We’d Like Clarified
Was there a change to the structured‑output JSON Schema validator?

If so, what changed, and when?

Is the validator expected to be backward‑compatible with previously accepted schemas?

Is there a documented subset or profile of JSON Schema that the validator supports?

Can OpenAI provide versioning or changelogs for validator behavior, similar to model releases?

Why This Matters
Structured output is a lot less useful if the schema contract is unstable.
If validator behavior can change without notice or versioning, it undermines the determinism that structured output is meant to provide.

This is a fair complaint. Structured output is usually used exactly because people need a stable contract, so a schema passing for weeks & weeeks and then failing overnight is pretty painful in production.

it would still be helpful to have a validator changelog or versioned schema profile…otherwise teams can’t tell whether they made a mistake or whether server-side validation behavior changed.