response-property-schema-became-false
Response property schema became the boolean `false`.
Not breaking (level: info)
oasdiff records this in the changelog but does not fail CI by default. Clients that worked under the old contract still work, so existing clients are not affected.
Mitigation
This is informational because narrowing what the server returns does not invalidate clients. A schema that accepts no value at all usually indicates an error in the specification, since the server cannot produce a conforming response.
Change its severity
oasdiff reports response-property-schema-became-false as informational, so it does not fail CI. To treat it as a warning or an error under your own compatibility policy, or to turn it off, set its level in a severity-levels file:
Put one rule per line; the level can be err, warn, or info, or none to disable the check entirely:
# severity.txt
response-property-schema-became-false errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt