Hi, I am wrapping my head around the Diamond Pact Nirvana step, in specific i am trying to set the "main" tag after my PR is merged to the main branch. But since a "merge" to the main branch creates a new commit I am having the problem, that I cannot call the broker to tag this version with "main", because the PACT version that got published to the broker is the head commit sha of the feature branch. There is technically with github actions no problem to simply add the tag to the correct version (git sha of the feature branch), but this is a bit dirty I think, as this git commit is not going to be the one that is deployed to prod, but the merge commit does. Has anyone had this problem too?

Every build (i.e. every commit) should have passing tests (including contract tests) before deploying. There's an optimisation in the broker to pre-verify a new contract version if the content is the same as an existing contract, so you don't really have to worry about verification performance.