-
Notifications
You must be signed in to change notification settings - Fork 166
Issues: OpenAPITools/openapi-diff
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Markdown output does not specify whether the change is backward-compatible or not
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
Render capabilities
Issue related to output rendering
Schema description update should be considered as a metadata change
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
duplicate
Deleted or renamed properties are marked as backwards compatible
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
No backward compatible changes in Schema are marked as Compatible
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
Removing a mandatory or optional property in the input data : breaking change ?
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
question
incompatible api diff result when one of property in model becomes not required
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
[2.1.0-beta.6 and oas-3.1.0] Request body property data type change is detected as compatible or no_change
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
False positive when adding optional property
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
Increasing the maxLength property for a String field is considered a breaking change while Decreasing it is considered as Backward compatible.
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
Do not fail with breaking changes when major version is bumped
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
enhancement
Removing a Query parameter is considered a breaking change while removing a Request Body parameter isn't
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
help wanted
Consider removal of deprecated elements as compatible
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
Removing a security scheme is considered incompatible
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
question
False positive breaking change when making a required request body optional
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
Adding a new optional property to the request/response body is considered backward incompatible.
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
PUT new attribute backwards compatibility optional
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
question
Refactoring a schma with "$ref" results in false positive breaking change
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
help wanted
Add documentation for detectable breaking/non-breaking changes
Breaking/Non-Breaking classification
Issues related to Breaking/Non-Breaking changes classification
enhancement
ProTip!
Updated in the last three days: updated:>2025-06-01.