response-body-default-value-changed
Response body default value changed.
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.
What this check detects
The `default` of the response body schema changed. As with a response property default, this documents the value used when the field is unset and does not change what shapes the response can take.
oasdiff reports this as informational.
Example
The documented default for the response body changed from 0 to 1; the contract shape is unchanged.
Change its severity
oasdiff reports response-body-default-value-changed 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-body-default-value-changed errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt