Prior to Vercel, we ran our frontend service in Kubernetes, and had CI/CD handled within Github Actions. We had the calls to Pactflow as part of those workflows.
With Vercel, they manage the CI/CD process with their git integration, but they have no way to customise that process to tie in any of the Pactflow actions we had previously.
We do have the option of continuing to run our CI/CD in GitHub Actions still, which we can then use Pactflow how we did previously, but we lose some of the nice features of the Vercel git intergration.
I was hoping someone here might have had some nice working examples of Vercel and Pactflow working together, but I think the answer is really going to end up resulting in us having to have a tradeoff between changing how we use Pactflow, or losing some of the benefits of Vercel.