request-parameter-default-value-added

What this check detects

A `default` was added to a request parameter that had none. When a client omits the parameter, the server now substitutes the default instead of treating it as unset, which can change the response a client was relying on.

oasdiff reports adding a default as breaking for this reason. Changing an existing default is treated more leniently (informational), because behavior for omitted values was already defined.

Example

A client that omitted "limit" previously got all results; now the server applies limit=20, changing the response.

Change its severity

oasdiff reports request-parameter-default-value-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
request-parameter-default-value-added err

Then pass it to oasdiff:

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