Unable to skip schema BC check for min and max properties

[jdesrochers-atpco]

When updating minProperties (increasing value) or maxProperties (decreasing value) of an attribute, there is no option in the backward compatibility checks to make the spec compatible.

Breaking example:
Before

        stuff:
          type: object
          minProperties: 1
          maxProperties: 10
          additionalProperties:
            type: string

After

        stuff:
          type: object
          minProperties: 5
          maxProperties: 10
          additionalProperties:
            type: string

Cannot be bypassed.

we should have a BC configuration property to manage this situation

[jdesrochers-atpco]

Suggested a solution for this issue in PR: #853

[jdesrochers-atpco]

Thanks for merging my PR @DrSatyr. Do you have any plan for a 2.1.5 release that would include this contribution? I just need to know if we wait for it, or if we update our CI/CD pipeline to use a local snapshot version.

[DrSatyr]

I will create a release today

[jdesrochers-atpco]

I will create a release today

Hi @DrSatyr, just following up on the next release. Any chance you can create it by next Monday.

Thanks

[DrSatyr]

@jdesrochers-atpco released!

[ThiruAI]

@jdesrochers-atpco released!

@DrSatyr we don' t still see 2.1.5 release version. is it going to take some time. https://github.com/OpenAPITools/openapi-diff/releases

[jdesrochers-atpco]

Our process takes the CLI library from the maven central repo. Is there a delay until it can be available there?

[DrSatyr]

It should be available on the Maven Central, please check https://repo1.maven.org/maven2/org/openapitools/openapidiff/openapi-diff-core/2.1.5/

[ThiruAI]

It should be available on the Maven Central, please check https://repo1.maven.org/maven2/org/openapitools/openapidiff/openapi-diff-core/2.1.5/

Thanks. I see it now.