[dependabot]

Bumps oasdiff/oasdiff-action from 0.1.12 to 0.1.17.

Release notes

Sourced from oasdiff/oasdiff-action's releases.

v0.1.17

oasdiff v1.32.1: fixes the hang on cyclic schemas

Every action now runs oasdiff v1.32.1, which fixes the v1.32.0 hang on specs whose schemas reference each other in cycles (oasdiff #1252). A workflow on such a spec no longer runs until the job times out. Recursive schemas are handled as in v1.31.0 again, so the circularRef field of diff json/yaml output is back and the non-determinism of oasdiff #1230 is back until the next release; everything else from v1.32.0 is kept.

No changes to the actions themselves. oasdiff/oasdiff-action/*@v0 now points at this release.

v0.1.16

What's Changed

• ci: lint every shell surface with shellcheck and actionlint by @​reuvenharrison in oasdiff/oasdiff-action#204
• bump: oasdiff v1.32.0 by @​reuvenharrison in oasdiff/oasdiff-action#205

Full Changelog: oasdiff/oasdiff-action@v0.1.15...v0.1.16

v0.1.15

Highlights

Upgraded to oasdiff v1.31.0

All actions (breaking, changelog, diff, pr-comment, validate) now run on oasdiff v1.31.0 (#203). No workflow changes are needed: update your uses: ref and your existing inputs keep working. Two behavior changes are worth knowing before you upgrade:

• Some changes now fail breaking that previously passed. Removing a constraint such as maximum or minLength from a response or response header is now an error (the server may return values old clients never had to handle), and setting a constraint on a request parameter is an error for every constraint keyword. These are part of 106 new checks completing set/unset coverage for all constraint keywords. If a flagged change is intended, lower the specific check with a severity-levels file.
• Fewer false failures on read-only properties. Restricting a readOnly request property (or a writeOnly response property) no longer fails as breaking: such a property never appears in a request, so the change is reported at info with a comment saying why.

See the oasdiff v1.31.0 release notes for the full list.

Full Changelog: oasdiff/oasdiff-action@v0.1.14...v0.1.15

v0.1.14

Highlights

Upgraded to oasdiff v1.30.0

Every action now runs on oasdiff v1.30.0, the largest change to breaking-change detection since the checker was introduced. Severities are now derived from a single reviewed model of what each change does to the API contract, which corrected 36 checks and added 58 new ones, so the breaking and changelog actions may report differently on the same diff:

• Changes that now fail a breaking step: setting a bound (maxLength, minItems, multipleOf and friends) where none existed, removing a security requirement or adding a security scope, adding a branch or value to a response union.
• Changes that no longer fail: request parameter default changes, removing optional response properties and headers, dropping an allOf conjunct.
• New detection: OpenAPI 3.1 boolean schemas (items: false tuples), positional prefixItems comparison (reordering entries is now caught), OpenAPI 3.2 QUERY and custom methods, and constraint keywords that were previously unchecked (maxItems, maxProperties, minProperties, multipleOf, uniqueItems).

If a step starts failing on a change your team accepts, override that check's severity with severity-levels in .oasdiff.yaml in your repo; the full list of changed checks is in the oasdiff v1.30.0 release notes.

Full Changelog: oasdiff/oasdiff-action@v0.1.13...v0.1.14

v0.1.13

Highlights

Upgraded to oasdiff v1.29.1

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

... (truncated)

Commits

• 5e81b5c Merge pull request #206 from oasdiff/bump/oasdiff-v1.32.1
• a39a6df bump: oasdiff v1.32.1
• 95200b7 bump: oasdiff v1.32.0 (#205)
• 23f44d4 ci: lint every shell surface with shellcheck and actionlint (#204)
• 9c0494c bump: oasdiff v1.31.0 (#203)
• 54d7a75 bump: oasdiff v1.30.0 (#202)
• 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)
• 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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 184299dc-422a-4549-b09f-d9cdbda3ffae

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[dependabot]

Superseded by #44.