response-required-property-became-not-write-only
Response required property became not write-only.
directionresponseareaschemakindmutabilityactionchange
Potentially breaking (level: warning)
oasdiff reports this as a warning: it breaks clients only in some cases, so it is surfaced for review rather than failing CI outright.
Mitigation
This is valid only if the property was always returned before the specification changed.
Change its severity or ignore it
To change the severity oasdiff assigns to response-required-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-required-property-became-not-write-only errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txtSetting the level to none disables the check, so it is no longer reported at all.