response-body-multiple-of-specialized

Mitigation

This change is not breaking because the new multipleOf is an integer multiple of the old one, so every value the server may now produce was already valid before.

Change its severity

oasdiff reports response-body-multiple-of-specialized 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-multiple-of-specialized err

Then pass it to oasdiff:

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