response-optional-property-became-not-write-only

Response optional property became not write-only.

directionresponseareaschemakindmutabilityactionchange

Not breaking (level: info)

oasdiff reports this in the changelog but does not treat it as a breaking change, so it does not fail CI by default.

Change its severity or ignore it

To change the severity oasdiff assigns to response-optional-property-became-not-write-only, list its id and a level in a severity-levels file, one rule per line. The level can be err, warn, or info, or none to disable the check entirely:

# severity.txt
response-optional-property-became-not-write-only err

Then pass it to oasdiff:

oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt

Setting the level to none disables the check, so it is no longer reported at all.

Related schema rules

Browse all 500 checks →