-
Notifications
You must be signed in to change notification settings - Fork 163
Insights: OpenAPITools/openapi-diff
Overview
-
- 2 Merged pull requests
- 0 Open pull requests
- 0 Closed issues
- 1 New issue
Could not load contribution data
Please try again later
2 Pull requests merged by 1 person
-
build(deps): bump org.jacoco:jacoco-maven-plugin from 0.8.12 to 0.8.13
#765 merged
Apr 3, 2025 -
build(deps): bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.2 to 3.5.3
#764 merged
Apr 3, 2025
1 Issue opened by 1 person
-
Markdown output does not specify whether the change is backward-compatible or not
#766 opened
Apr 5, 2025
17 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Schema description update should be considered as a metadata change
#694 commented on
Apr 5, 2025 • 0 new comments -
Deleted or renamed properties are marked as backwards compatible
#673 commented on
Apr 5, 2025 • 0 new comments -
No backward compatible changes in Schema are marked as Compatible
#611 commented on
Apr 5, 2025 • 0 new comments -
Removing a mandatory or optional property in the input data : breaking change ?
#599 commented on
Apr 5, 2025 • 0 new comments -
incompatible api diff result when one of property in model becomes not required
#535 commented on
Apr 5, 2025 • 0 new comments -
[2.1.0-beta.6 and oas-3.1.0] Request body property data type change is detected as compatible or no_change
#528 commented on
Apr 5, 2025 • 0 new comments -
Add documentation for detectable breaking/non-breaking changes
#138 commented on
Apr 5, 2025 • 0 new comments -
False positive when adding optional property
#490 commented on
Apr 5, 2025 • 0 new comments -
Adding a new optional property to the request/response body is considered backward incompatible.
#264 commented on
Apr 5, 2025 • 0 new comments -
PUT new attribute backwards compatibility optional
#251 commented on
Apr 5, 2025 • 0 new comments -
Increasing the maxLength property for a String field is considered a breaking change while Decreasing it is considered as Backward compatible.
#461 commented on
Apr 5, 2025 • 0 new comments -
Do not fail with breaking changes when major version is bumped
#460 commented on
Apr 5, 2025 • 0 new comments -
Removing a Query parameter is considered a breaking change while removing a Request Body parameter isn't
#412 commented on
Apr 5, 2025 • 0 new comments -
Consider removal of deprecated elements as compatible
#371 commented on
Apr 5, 2025 • 0 new comments -
Removing a security scheme is considered incompatible
#330 commented on
Apr 5, 2025 • 0 new comments -
False positive breaking change when making a required request body optional
#329 commented on
Apr 5, 2025 • 0 new comments -
Output in text and markdown not equivalent (text output incomplete)
#620 commented on
Apr 5, 2025 • 0 new comments