api-major-version-not-bumped
A breaking change was detected but the major version did not increase.
areainfokindlifecycleactionincrease
Not breaking (level: info)
oasdiff records this in the changelog but does not fail CI by default. It is backward compatible, so existing clients are not affected.
Change its severity
oasdiff reports api-major-version-not-bumped 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
api-major-version-not-bumped errThen pass it to oasdiff:
oasdiff changelog base.yaml revision.yaml --severity-levels severity.txt