- Notifications
You must be signed in to change notification settings - Fork 164
Insights: OpenAPITools/openapi-diff
Overview
- 5 Merged pull requests
- 0 Open pull requests
- 2 Closed issues
- 1 New issue
Could not load contribution data
Please try again later
1 Release published by 1 person
- 2.1.0
published
Apr 26, 2025
5 Pull requests merged by 3 people
- build(deps): bump org.apache.commons:commons-configuration2 from 2.11.0 to 2.12.0
#778 merged
Apr 29, 2025 - Issue 422
#771 merged
Apr 26, 2025 - Fix: Address Sonar Blocker issues
#775 merged
Apr 24, 2025 - DrSatyr/issue212
#774 merged
Apr 24, 2025 - build(deps): bump org.apache.commons:commons-collections4 from 4.4 to 4.5.0
#773 merged
Apr 23, 2025
2 Issues closed by 1 person
- StackOverflowError during Processing
#422 closed
Apr 26, 2025 - [bug] support of breaking changes for "anyOf"
#212 closed
Apr 24, 2025
1 Issue opened by 1 person
- Unify Handling of allOf/anyOf and oneOf in Diff logic
#772 opened
Apr 22, 2025
21 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.
- [OpenAPI 3.1.0 support] JsonSchema type changes not handled.
#745 commented on
Apr 24, 2025 • 0 new comments - Comparing OpenAPI 3.0.1 to 3.1.0 does not work
#755 commented on
Apr 24, 2025 • 0 new comments - Add documentation for detectable breaking/non-breaking changes
#138 commented on
Apr 24, 2025 • 0 new comments - Refactoring a schma with "$ref" results in false positive breaking change
#192 commented on
Apr 24, 2025 • 0 new comments - PUT new attribute backwards compatibility optional
#251 commented on
Apr 24, 2025 • 0 new comments - Adding a new optional property to the request/response body is considered backward incompatible.
#264 commented on
Apr 24, 2025 • 0 new comments - Consider removal of deprecated elements as compatible
#371 commented on
Apr 24, 2025 • 0 new comments - False positive breaking change when making a required request body optional
#329 commented on
Apr 24, 2025 • 0 new comments - Removing a security scheme is considered incompatible
#330 commented on
Apr 24, 2025 • 0 new comments - Do not fail with breaking changes when major version is bumped
#460 commented on
Apr 24, 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 24, 2025 • 0 new comments - False positive when adding optional property
#490 commented on
Apr 24, 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 24, 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 24, 2025 • 0 new comments - No backward compatible changes in Schema are marked as Compatible
#611 commented on
Apr 24, 2025 • 0 new comments - incompatible api diff result when one of property in model becomes not required
#535 commented on
Apr 24, 2025 • 0 new comments - Removing a mandatory or optional property in the input data : breaking change ?
#599 commented on
Apr 24, 2025 • 0 new comments - Deleted or renamed properties are marked as backwards compatible
#673 commented on
Apr 24, 2025 • 0 new comments - Markdown output does not specify whether the change is backward-compatible or not
#766 commented on
Apr 24, 2025 • 0 new comments - Schema description update should be considered as a metadata change
#694 commented on
Apr 24, 2025 • 0 new comments - --json output is absurdly huge
#562 commented on
Apr 28, 2025 • 0 new comments