Hi all! URGENT. It's blocking our release right now... We're facing the issue with tagging pacticipant with tag, e.g. prod. Pact Broker version: 2.88.0.0 We have multiple versions of a pacticipant. For example latest version was 5.0.0 which has prod tag (it is marked with blue color). We're pushed new version 6.0.0 and trying to tag that version as we did it multiple times previously. But in Pact Broker i see that new version (6.0.0) was tagged as prod but not marked with clue color and when we doing request to retrieve latest version by tag for that pacticipant it returns 5.0.0. In other words "latest" flag is not switched to a newest version despite of the newest (6.0.0 version) was tagged as prod. Could anyone help us with that ASAP?

Hi @danilchican are you around now?

Not sure if this is helpful @danilchican re the above env var https://pact-foundation.slack.com/archives/C9VPNUJR2/p1653426793243039?thread_ts=1653412787.937529&cid=C9VPNUJR2

The problem was related to created at date for the version. We found that previously (one year before) when we tested Pact Broker versioning, we left some test versions which are equal to our currently newest versions and as you understand

order

field in

versions

table was too small to be able to override latest version for the same tag.

@danilchican the new environments and deployments feature will not have this issue

@Beth (pactflow.io/Pact Broker/pact-ruby), could you please share the link to it?

Background reading: https://docs.pact.io/blog/2021/07/04/why-we-are-getting-rid-of-tags Site docs: https://docs.pact.io/pact_broker/branches https://docs.pact.io/pact_broker/recording_deployments_and_releases