build(deps): bump oasdiff/oasdiff-action/breaking from 0.1.10 to 0.1.12

[dependabot]

Bumps oasdiff/oasdiff-action/breaking from 0.1.10 to 0.1.12.

Release notes

Sourced from oasdiff/oasdiff-action/breaking's releases.

v0.1.12

Highlights

Upgraded to oasdiff v1.28.0

Every action (breaking, changelog, diff, pr-comment, validate) now runs on oasdiff v1.28.0, up from v1.26.1 in the previous release (#193, #194). No workflow changes are needed: bump the tag on your uses: lines and your existing inputs keep working.

- uses: oasdiff/oasdiff-action/breaking@v0.1.12
  with:
    base: 'main-openapi.yaml'
    revision: 'openapi.yaml'

Full Changelog: oasdiff/oasdiff-action@v0.1.11...v0.1.12

v0.1.11

Every action now runs on oasdiff v1.27.0, which adds a versioning policy and more validate checks.

Action behaviour change: include-checks no longer elevates a check

If your workflow uses the include-checks input to make an optional check fail the build, that step will stop failing on this release. oasdiff v1.27.0 retires the optional-checks mechanism: every check now runs, and severity is the only lever. --include-checks is accepted, prints a deprecation notice, and is otherwise ignored, so a check you elevated with it now reports at its default severity instead of as an error.

To keep the gate, set the severity explicitly. Put a .oasdiff.yaml at the root of the repo the action runs in:

# .oasdiff.yaml
severity-levels: .oasdiff-levels.txt

# .oasdiff-levels.txt
response-non-success-status-removed    err

and drop the include-checks input from the workflow. The same file is how you disable a check (none) or downgrade one (warn, info).

Highlights

New: catch a breaking change that shipped without a major version bump

If you version your API with semantic versioning, a breaking change is supposed to come with a major version bump. oasdiff now compares info.version on each side against the changes it found and reports a breaking change that did not get one. Three findings, one per way it can go wrong:

Check id	Reported when a breaking change was detected and
api-version-not-bumped	the version is unchanged
api-version-decreased	the version moved backwards, e.g. 2.0.0 to 1.0.0
api-major-version-not-bumped	the version moved, but not the major, e.g. 1.0.0 to 1.1.0

They are informational by default, so no workflow starts failing on upgrade. To enforce the policy, add the ids to the severity-levels file described above:

... (truncated)

Commits

• 033c15c bump: oasdiff v1.28.0 (#194)
• b7c3ade bump: oasdiff v1.27.0 (#193)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)