api-deprecated-sunset-missing

Endpoint deprecated without sunset date.

areapathskindlifecycleactionchange

Breaking change (level: error)

oasdiff reports this as a breaking change by default. It can break existing API clients, so CI fails on it unless you downgrade its severity.

Change its severity or ignore it

To change the severity oasdiff assigns to api-deprecated-sunset-missing, 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
api-deprecated-sunset-missing warn

Then pass it to oasdiff:

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

Setting the level to none disables the check, so it is no longer reported at all.

Related paths rules

Browse all 500 checks →