How to handle different pacts being published with the same version number

[bethesque]

Background

The problem I'm about to describe already exists, but had been more clearly highlighted as I've tried to work through design options for supporting branches as a first class concept in the broker.

While we advise that the application version number used to publish pacts to the broker is unique per commit, many users still publish pacts with a semi-hardcoded version number (eg. the semantic version number from the json package file which only gets updated on release). This means that the pact content for what is considered the application version 1.2.3 changes over time. When pacts are published from different branches with the same version number, and the tags are set from the branches, a single pacticipant version may appear to the broker to have been built by multiple different branches, and to have had it's pact content revised multiple times.

eg.

• Publish pacts from version 1.0.0, commit abc, branch (ie. tag) main.
• Make a branch, feat/x. Make a change to the pact. Publish pacts version 1.0.0 (again), commit def, branch (ie. tag) feat/x.
• Now version 1.0.0 has the tags main and feat/x, and the content from the feat/x branch.
• can-i-deploy runs on the main branch for version 1.0.0. It has the content from feat/x and so fails as feat/x has not been implemented.

TODO finish this.