Hi there, Will the support of

tag

be removed in the upcoming versions or it will be kept for backward compatibility

It will be kept, there are some use cases for them. Why do you ask?

Thanks Matt, Sorry for the late reply. We have complicated set of release process (for a legacy app) and been thinking to use tags to solve an issue with selecting right version of consumer contracts to verify. Looks like, we need to understand more about the release process because there is much more in it. Once we get the info, we will see whether use of environments is enough instead of complicated setup. Will reach out if we cant solve or where we see tag can be used to get your view as well. Regarding your comment about the use cases of tags, I thought it is preferred to use

Branch

and

Environment

instead of tags for this. Does other use cases you are referring to is related to feature toggles or may be something more.

Does other use cases you are referring to is related to feature toggles or may be something more.

I don’t follow this sentence, sorry

no worries, I meant to ask the you've said there are some use cases for tags. I was curious to know about the additional use cases because we are moving away from tags to branches/environments as recommended from pact. Hope this helps

oh right. Yes, that’s the only primary “feature” related use case

cool, thanks @Matt (pactflow.io / pact-js / pact-go). much appreciated