v0.1.13

Highlights

Upgraded to oasdiff v1.29.1

All actions now run on oasdiff v1.29.1 (#194, #201).

include-checks is deprecated: use .oasdiff.yaml instead

oasdiff retired the optional-checks mechanism behind include-checks, so the input has been silently doing nothing. The actions no longer forward it to the CLI and instead emit a warning annotation explaining the replacement. Workflows that still pass the input keep working rather than failing on an unknown flag (#197).

To make a specific check fail the build, list it in a severity-levels file and point .oasdiff.yaml at it:

# .oasdiff.yaml
severity-levels: ./oasdiff-levels.txt
fail-on: ERR

# oasdiff-levels.txt
api-version-not-bumped    err

Anonymous delivery reporting for review comments

The breaking, changelog, and pr-comment actions now send oasdiff.com one anonymous event per run saying whether the review link was posted as a PR comment or fell back to the job summary, so the defaults can be improved. No repo, organization, or user identity is sent, failures never affect the run, and setting OASDIFF_INTERNAL=1 skips it entirely (#195).

Fixes

• A failed comparison no longer reads as a clean result. When oasdiff could not load or parse a spec, the breaking and diff actions failed the step but still wrote No breaking changes / No changes to the step output, job summary, and PR comment, and the validate action published findings=0 with all counts at zero for an unloadable spec. All three now stop as soon as the comparison fails, so anything reading the outputs, or running with continue-on-error, sees the failure instead of a clean report. Regression tests pin the behavior for each action (#199, thanks @lucas-monteiro-g, who found this and opened #198 with a fix and a test fixture).

Full Changelog: v0.1.12...v0.1.13