hello lovely pact folks, I wanted to double check if there's a particular reason why I'm not able to use

--latest TAG

with

record-deployment

in the same way as

can-I-deploy

, in place of using a

--version

?

I guess the main reason is it’s not super accurate (it points at a moving version, rather than a fixed one). e.g. what if another pact is tagged when you run that command, it could lead to surprising results. When you deploy your software, presumably you should know which one you’re releasing?

hi Matt, thanks for the response! Yes we should, we're just checking how to best/easiest approach releases right now with a new tool, and this question was raised, to which I did not know the answer to 😄 our tags should be unique FWIW so that didn't come to mind, but it makes total sense. Thanks again!

ah, I see what you’re saying. You’re tagging a consumer with e.g. a release tag. I can understand that, it seems reasonable. Tag_s were_ a proxy for things like branches, so the versions could move frequently and thus was not a safe identifier.

yeah the tags we want to follow for marking as released will be semantic versioning, everytime the branch is re-run or a new release is raised, a new version is bumped, so in theory each attempt to release would have its own unique semantic version, hence the us seeing if we could use it to do the deploy and record commands, without needing that extra step of using the tag to fetch the latest version, to then run the commands