Hi 👋 . Have there been very recent changes (yesterday/today) released in the pact broker contract format validation logic? Suddenly contracts that used to be successfully published to Pactflow are now being rejected for not meeting OpenAPI spec format protocols. Examples of errors we're seeing: - Missing info.version field being rejected - property '/paths/.../type' is not one of: ["array", "boolean", "integer", "number", "object", "string"] — for schemas using type: null - property '/paths/.../required' is invalid — for schemas with required: [] (empty array) - property '/paths/.../parameters' is invalid: error_type=uniqueItems — for duplicate parameter definitions - property '/paths/.../items/items' is not of type: object — for array items defined as array literals instead of schema objects These contracts have been publishing successfully for weeks/months without changes. Were stricter OAS 3.0 validation rules recently enforced?

Hi Marlin, I believe we did release a change overnight to improve validation of OpenAPI specs - it’s a highly requested feature, as an invalid OAD will fail our comparison down the line. I’ve passed this to engineering to review - Out of caution, I think we’re going to revert to ensure it’s not causing any widespread issues. Can you please DM me your account info so that we can chat privately (if you would prefer) so that I can see if this is a false positive in your case? Apologies for the disruption.

Thanks Matt. I've DMed you. In general I think the stricter requirements are probably a good thing, it just took us by surprise.