PactJs breaking change demo

We make a breaking change, we update our tests, and we get blocked by Pact because of how it will break integration in a future deployment - even though a full stack of tests are looking green in our own repo.
Then we go through the nuances of how to introduce a breaking change in a collaborative way together with our consumers.
It is a tri-way setup with traditional pactjs consumer driven + provider driven (bi-directional) contract testing, alongside with Cypress e2e, cy schema test plugin, Optic schema verification, Zod-to-OpenAPI, jest, cyct
Here are the collaborating PRs:
Provider: github.com/mur...
Consumer: github.com/mur...
Bi-directional Consumer: github.com/mur...
Blog post about how it all works dev.to/muratke...