response-body-media-type-item-schema-added
Response media-type item schema added.
directionresponsearearesponseskindexistenceactionadd
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.
Change its severity
oasdiff reports response-body-media-type-item-schema-added 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-media-type-item-schema-added errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txtRelated responses rules
- response-body-content-encoding-changed
- response-body-content-media-type-changed
- response-body-media-type-item-schema-removed
- response-body-media-type-item-schema-removed-untyped
- response-body-media-type-schema-added
- response-body-media-type-schema-removed
- response-media-type-added
- response-media-type-name-changed