Version 0.2.0 introduces breaking change due to version upgrade about openapi-schema-validator HOT 7 CLOSED

@gberaudo 1.x is planned to be stable for production, 0.x is marked as beta and you can expect issues.

@RobbeSneyders I think you're right we dropped support for jsonschema3 too early. I made dependency matrix for various versions

from openapi-schema-validator.

Fair point on increasing the minor version while still on 0.X.X, dependents should probably define boundaries on the minor version at this stage. It might be good to note though that caret versioning seems poetry specific, and not completely aligned with semantic versioning which is what most people will expect.

I still think my proposal is valid though. At this point the iter_errors change is unnecessary and limits the compatibility of open-schema-validator with both jsonschema and other packages depending on it.

from openapi-schema-validator.

Thanks @p1c2u, that matrix provides a great overview.

Does that mean you want to release a patch version 0.2.1 reverting #25, as proposed?

from openapi-schema-validator.

@RobbeSneyders
Yes I will do that.

from openapi-schema-validator.

Thank you for your help. Patch version 0.2.1 released hence closing.

from openapi-schema-validator.

Hi @RobbeSneyders

that was my intention to follow new interface of jsonschema 4.x-5.x with version 0.2.x and let 0.1.x support jsonschema 3.x.

I didn't change to version 1.x because the project is not mature enough for this, instead I changed the left-most non-zero digit to follow Caret versioning

from openapi-schema-validator.

Hi @p1c2u,

I didn't change to version 1.x because the project is not mature enough for this, instead I changed the left-most non-zero digit to follow Caret versioning

Do you consider versions 0.x to be ready for production? (and more generaly openapi-core ?

from openapi-schema-validator.