Hi, As of Friday morning we're getting a large amount of failures in contract comparison for APIs that we haven't changed. The main types we are seeing are • Request body is incompatible with the request body schema in the spec file: must be object • Request content type header is not defined but spec specifies mime-types to consume • Response Content-Type header is defined but the spec does not specify any mime-types to produce Would anyone be able to help with this please? It really doesn't look to me like we've actually broken our contracts, so I'm wondering if it's a Pact bug.

Hi Becky, are you a cloud or on prem customer? I'll follow up tomorrow to check our changlog. Have you published recently? We have released some changes a few weeks ago that I'm aware of but they may not have impacted you until you've published. If you like, you could raise a support ticket. Please ensure you include the OAS and Pact file causing the issue so we can investigate.. (See howtosmartbearsupport)

Please create a ticket here with the issue details so that we can properly track the resolution and the PactFlow product support team will continue to work through it with you: https://support.smartbear.com/pactflow/message

Thanks for the quick response. We've managed to narrow down the cause after a lot of digging. Turns out that node 18.18.2 changed the behaviour of

JSON.stringify

so it was writing all our request bodies as strings of JSON instead of as JSON objects!

argh! Really?