request-body-default-value-changed
Request body default value modified.
directionrequestareaschemakindvaluesactionchange
Not breaking (level: info)
oasdiff records this in the changelog but does not fail CI by default. Requests that were valid under the old contract are still valid, so existing clients are not affected.
Example
Before
After
1requestBody:1requestBody:
2 content:2 content:
3 application/json:3 application/json:
4 schema:4 schema:
5 type: integer5 type: integer
6 default: 106 default: 20
The value applied when the client omits the request body changed from 10 to 20.
Change its severity
oasdiff reports request-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
request-body-default-value-changed errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt