Hello I have a question about Pact and API versions. I've found the following question that was already answered before: https://pact-foundation.slack.com/archives/CLS16AVEE/p1680267252981199 So, according to the answers above, Pact is capable of dealing with multiple API versions. I was indeed able to successfully publish a manually prepared swagger.json file with two paths /api/v1/mail and /api/v2/mail to Pactflow. But I wonder whether this is the recommended way? I have doubts because the "dotnet swagger" command, which is the standard command for generating swagger files in dotnet projects, does not seem to support the generation of a swagger file with multiple versions, or at least not in a straightforward way. The "dotnet swagger" command seems to be designed to create one API version per file: For example: dotnet swagger v1 myapp.dll --output v1/swagger.json or dotnet swagger v2 myapp.dll --output v1/swagger.json So, the question arises whether it would be possible to publish two files with two different API versions for the same provider version? Or is one file with two paths the only (and the proper) way to publish two versions for the same provider version? Or generally speaking, what is the proper way to handle versioning of APIs with regards to Pact?