Skip to content

chore(deps): update oasdiff/oasdiff-action action to v0.1.24 - #38

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/oasdiff-oasdiff-action-0.1.x
Nov 14, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/oasdiff-oasdiff-action-0.1.x

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
oasdiff/oasdiff-action action patch v0.1.23 → v0.1.24

Release Notes

oasdiff/oasdiff-action

v0.1.24

Compare Source

Every action now runs on oasdiff v1.38.0, which adds a way to gate on version bumps and names the file each change is in.

Highlights

Fail only when a breaking change ships without a major version bump

The breaking action's fail-on input takes a new value, MISSING-VERSION-BUMP:

- uses: oasdiff/oasdiff-action/breaking@v0.1.24
  with:
    base: 'main:openapi.yaml'
    revision: 'openapi.yaml'
    fail-on: MISSING-VERSION-BUMP

The step passes when the breaking changes come with a major increase in info.version, and fails when they do not. Annotations are unaffected, so reviewers see every breaking change on the Files changed tab either way, and the step log says how the version was judged:

versioning policy: violated. info.version is still 1.0.0.

See Version Bumps and Breaking Changes.

This replaces the api-version-not-bumped, api-version-decreased and api-major-version-not-bumped checks, which are retired. If a severity-levels file named in your .oasdiff.yaml lists one of those ids, it now fails to load like any other unknown id, so remove those lines when you upgrade.

Annotations name the file each change is in
  • A removal is annotated in the base spec, where the removed element still is, instead of the revision, which no longer has it.
  • A change inside a $ref'd file is annotated in that file instead of in the root document.
  • A change to info.version is annotated on that line.

Fixes

  • A description edit inside an anonymous allOf, anyOf or oneOf branch is no longer reported as a branch added and removed. Editing a description under a oneOf in a response schema used to produce response-property-one-of-added and response-property-one-of-removed for what was only a documentation change (oasdiff #​1404).
  • A description an inline to $ref refactor carries is reported again. Inline and $ref branches that validate the same are matched as one branch (on by default), and a matched pair was dropped whole, so a description that differed between the inline branch and the component replacing it was reported nowhere (oasdiff #​1408).
  • The validate action no longer fails on a callback cycle, which the other actions already handled (oasdiff #​1401).

Full Changelog: oasdiff/oasdiff-action@v0.1.23...v0.1.24


Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions

Copy link
Copy Markdown
Contributor

Test results

  204 files    204 suites   1m 33s ⏱️
  549 tests   549 ✅  0 💤 0 ❌
1 647 runs  1 555 ✅ 92 💤 0 ❌

Results for commit b3573a5.

@renovate
renovate Bot merged commit cfbb43c into main Nov 14, 2026
12 checks passed
@renovate
renovate Bot deleted the renovate/oasdiff-oasdiff-action-0.1.x branch November 14, 2026 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants