chore: bump oasdiff/oasdiff-action/breaking from 0.0.21 to 0.1.13

[dependabot]

Bumps oasdiff/oasdiff-action/breaking from 0.0.21 to 0.1.13.

Release notes

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

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: oasdiff/oasdiff-action@v0.1.12...v0.1.13

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

... (truncated)

Commits

• 2649ebe bump: oasdiff v1.29.1 (#201)
• 5ad1d21 Stop reporting a failed comparison as a clean result (#199)
• aac8c66 Stop pretending include-checks works, and point it at .oasdiff.yaml (#197)
• b803cbd report anonymously whether the review comment could be posted (#195)
• 033c15c bump: oasdiff v1.28.0 (#194)
• b7c3ade bump: oasdiff v1.27.0 (#193)
• 0ab8ad2 bump: oasdiff v1.26.1 (#192)
• 45c956e bump: oasdiff v1.26.0 (#191)
• 4bdf890 bump: oasdiff v1.25.1 (#190)
• 35b3224 bump: oasdiff v1.24.0 (#188)
• Additional commits viewable 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)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Missing linked issue

This PR does not reference a tracking issue in its body. Every PR must link to an issue in this repository so we can trace work back to a planned change.

How to fix

1. Edit the PR description and add a line like Closes #123, Fixes #123, or Resolves #123 referring to an open issue in artifact-keeper/artifact-keeper-api.
2. Save the description. This check will re-run automatically.

Accepted keywords (case-insensitive, any tense): close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved.

Policy reference: see the PR template.

Maintainer bypass: apply the no-issue-required label to this PR to skip the check (use sparingly, e.g. for trivial typo fixes or release-tag chores).